From 5d8c88d7c2267ed6b839956045c1e924559b9168 Mon Sep 17 00:00:00 2001
From: Fabian Affolter <fabian@affolter-engineering.ch>
Date: Tue, 30 May 2017 12:33:22 +0200
Subject: [PATCH] Add content from #2330

---
 .../_docs/ecosystem/nginx_subdomain.markdown  | 116 ++++++++++++++++++
 source/_includes/asides/docs_navigation.html  |   1 +
 2 files changed, 117 insertions(+)
 create mode 100644 source/_docs/ecosystem/nginx_subdomain.markdown

diff --git a/source/_docs/ecosystem/nginx_subdomain.markdown b/source/_docs/ecosystem/nginx_subdomain.markdown
new file mode 100644
index 00000000000..2bc9413b7e4
--- /dev/null
+++ b/source/_docs/ecosystem/nginx_subdomain.markdown
@@ -0,0 +1,116 @@
+---
+layout: page
+title: "NGINX Configuration"
+description: "Configure Nginx to work with Home Assistant as a subdomain"
+date: 2016-06-20 13:05
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+This example demonstrates how you can configure NGINX to act as a proxy for Home Assistant.
+
+This is useful if you want to have:
+
+ * a subdomain redirecting to your home assistant instance
+ * several subdomain for several instance
+ * HTTPS redirection
+
+#### {% linkable_title Subdomain %}
+
+So you already have a working NGINX server available at example.org. Your Home Assistant is correctly working on this web server and available at http://localhost:8123
+
+To be able to access to your Home Assistant instance by using https://home.example.org, create file `/etc/nginx/sites-enabled/homeassistant` (or symlink via `/etc/nginx/sites-available`) and add the following:
+
+```nginx
+server {
+    listen       443 ssl;
+    server_name  home.example.org;
+    
+    ssl on;
+    ssl_certificate /etc/nginx/ssl/home.example.org/home.example.org-bundle.crt;
+    ssl_certificate_key /etc/nginx/ssl/home.example.org/home.example.org.key;
+    ssl_prefer_server_ciphers on;
+
+    location / {
+        proxy_pass http://localhost:8123/;
+        proxy_set_header Host $host;
+    }
+
+    location /api/websocket {
+        proxy_pass http://localhost:8123/api/websocket;
+        proxy_set_header Host $host;
+
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+
+    }
+}
+```
+
+If you don't want HTTPS, you can change `listen 443 ssl` to `listen 80` or better, consider redirecting all HTTP to HTTPS. See further down.
+
+#### {% linkable_title Multiple Instance %}
+
+You already have Home Assistant running on http://localhost:8123 and available at home.example.org as describe before. The configuration file for this Home Assistant is available in `/home/alice/.homeassistant/configuration.yaml`.
+
+You want another instance available at https://countryside.example.org
+
+You can either :
+ * Create a new user, `bob`, to hold the configuration file in `/home/bob/.homeassistant/configuration.yaml` and run home assistant as this new user
+ * Create another configuration directory in `/home/alice/.homeassistan2/configuration.yaml` and run home assistant using `hass --config /home/alice/.homeassistant2/`
+
+In both solution, change port number used by modifying `configuration.yaml` file.
+
+```yaml
+http:
+  server_port: 8124
+  ...
+```
+
+Start Home Assistant: Now, you have another instance running on http://localhost:8124
+
+To access this instance by using https://countryside.example.org create the file `/etc/nginx/sites-enabled/countryside.example.org` (or symlink via `/etc/nginx/sites-available`) and add the following:
+
+```bash
+server {
+    listen       443 ssl;
+    server_name  countryside.example.org;
+    
+    ssl on;
+    ssl_certificate /etc/nginx/ssl/countryside.example.org/countryside.example.org-bundle.crt;
+    ssl_certificate_key /etc/nginx/ssl/countryside.example.org/countryside.example.org.key;
+    ssl_prefer_server_ciphers on;
+
+    location / {
+        proxy_pass http://localhost:8124/;
+        proxy_set_header Host $host;
+    }
+
+    location /api/websocket {
+        proxy_pass http://localhost:8124/api/websocket;
+        proxy_set_header Host $host;
+
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+
+    }
+}
+```
+
+#### {% linkable_title HTTP to HTTPS redirection %}
+
+Add to your `/etc/nginx/sites-enabled/default`
+
+```bash
+server {
+    listen       80 default_server;
+    server_name  example.tld;
+
+    return 301 https://$host$request_uri;
+}
+```
+
diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html
index 2c7957a23ff..9188337f0c9 100644
--- a/source/_includes/asides/docs_navigation.html
+++ b/source/_includes/asides/docs_navigation.html
@@ -188,6 +188,7 @@
             <ul>
               <li>{% active_link /docs/ecosystem/apache/ Apache %}</li>
               <li>{% active_link /docs/ecosystem/nginx/ NGINX %}</li>
+              <li>{% active_link /docs/ecosystem/nginx_subdomain/ NGINX with subdomain%}</li>
               <li>{% active_link /docs/ecosystem/tor/ Tor Onion Service %}</li>
             </ul>
           </li>