From bb4a8c998e147c5c55e6c75a15cd8acac70820fb Mon Sep 17 00:00:00 2001 From: Tom Hacohen Date: Sun, 29 Nov 2020 17:02:49 +0200 Subject: [PATCH] README: updateinformation about passing the Host header As mentioned in https://github.com/etesync/server/issues/75#issuecomment-735370709 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 12f7747..cfb0be9 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ There is also a [wikipage](https://github.com/etesync/server/wiki/Basic-Setup-Et Some particular settings that should be edited are: * [`ALLOWED_HOSTS`](https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-ALLOWED_HOSTS) -- this is the list of host/domain names or addresses on which the app -will be served +will be served. For example: `etebase.example.com` * [`DEBUG`](https://docs.djangoproject.com/en/dev/ref/settings/#debug) -- handy for debugging, set to `False` for production * [`MEDIA_ROOT`](https://docs.djangoproject.com/en/dev/ref/settings/#media-root) @@ -78,6 +78,8 @@ Etebase is based on Django so you should refer to one of the following The webserver should also be configured to serve Etebase using TLS. A guide for doing so can be found in the [wiki](https://github.com/etesync/server/wiki/Setup-HTTPS-for-Etebase) as well. +The Etebase server needs to be aware of the URL it's been served as, so make sure to forward the `Host` header to the server if using a reverse proxy. For example, you would need to use the following directive in nginx: `proxy_set_header Host $host;`. + # Data locations and backups The server stores user data in two different locations that need to be backed up: