##  
  # You should look at the following URL's in order to grasp a solid understanding  
  # of Nginx configuration files in order to fully unleash the power of Nginx.  
  # https://www.nginx.com/resources/wiki/start/  
  # https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/  
  # https://wiki.debian.org/Nginx/DirectoryStructure  
  #  
  # In most cases, administrators will remove this file from sites-enabled/ and  
  # leave it as reference inside of sites-available where it will continue to be  
  # updated by the nginx packaging team.  
  #  
  # This file will automatically load configuration files provided by other  
  # applications, such as Drupal or Wordpress. These applications will be made  
  # available underneath a path with that package name, such as /drupal8.  
  #  
  # Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.  
  ##  
  
  server {  
      listen 80;  
      listen [::]:80;  
      server_name observium.errigal.com;  
      
      location / {  
          proxy_pass http://localhost:6001;  
          proxy_set_header host $host;  
          proxy_set_header x-real-ip $remote_addr;  
      }  
  }  
  
  server {  
      listen 80;  
      listen [::]:80;  
      listen 443 ssl http2;  
      listen [::]:443 ssl http2;  
      server_name docker.errigal.com;  
      
      ssl_certificate /etc/nginx/ssl/ssl_bundle.crt;  
      ssl_certificate_key /etc/nginx/ssl/private-key.pem;  
      
      location / {  
          proxy_pass http://localhost:5001;  
          proxy_set_header host $host;  
          proxy_set_header x-real-ip $remote_addr;  
      }  
  }  
  
  server {  
      listen 80;  
      listen [::]:80;  
      server_name registry.errigal.com;  
      
      location / {  
          proxy_pass https://registry.errigal.com;  
          proxy_set_header host $host;  
          proxy_set_header x-real-ip $remote_addr;  
      }  
  }  
  
  server {  
      listen 443 ssl http2;  
      listen [::]:443 ssl http2;  
      server_name registry.errigal.com;  
      
      ssl_certificate /etc/nginx/ssl/ssl_bundle.crt;  
      ssl_certificate_key /etc/nginx/ssl/private-key.pem;  
      
      location / {  
          proxy_pass https://localhost:5000;  
          proxy_set_header host $host;  
          proxy_set_header x-real-ip $remote_addr;  
      }  
  }  
  
  server {  
      listen 80;  
      listen [::]:80;  
      listen 443 ssl http2;  
      listen [::]:443 ssl http2;  
      server_name logsearch.errigal.com;  
      
      ssl_certificate /etc/nginx/ssl/ssl_bundle.crt;  
      ssl_certificate_key /etc/nginx/ssl/private-key.pem;  
      
      location / {  
          proxy_pass http://localhost:5601;  
          proxy_set_header Host $host;  
          proxy_set_header X-Real-IP $remote_addr;  
      }  
  }  
  
  server {  
      listen 80;  
      listen [::]:80;  
      listen 443 ssl http2;  
      listen [::]:443 ssl http2;  
      server_name opsjenkins.errigal.com;  
      
      
      ssl_certificate /etc/nginx/ssl/ssl_bundle.crt;  
      ssl_certificate_key /etc/nginx/ssl/private-key.pem;  
      
      location / {  
          proxy_pass http://localhost:8080;  
          proxy_set_header Host $host;  
          proxy_set_header X-Real-IP $remote_addr;  
      }  
  }  
  
  
  # Virtual Host configuration for example.com  
  #  
  # You can move that to a different file under sites-available/ and symlink that  
  # to sites-enabled/ to enable it.  
  #  
  #server {  
  #       listen 80;  
  #       listen [::]:80;  
  #  
  #       server_name example.com;  
  #  
  #       root /var/www/example.com;  
  #       index index.html;  
  #  
  #       location / {  
  #               try_files $uri $uri/ =404;  
  #       }  
  #}