In order to run over HTTPS* django requires the X-Forwarded-Proto header sent from the nginx proxy. I didn't add everything needed for TLS, but this header works with HTTP and HTTPS so I figure it might save a few people some time if they ever decide to secure their installation.
\* specifically, I noticed that image URLs are requested over HTTP instead of HTTPS even when the main page is HTTPS until this header is sent
I just went through a manual install on DietPi / Debian Unstable, and found that the manual needed some improving, this method works, whereas following the original manual was not a success for me.
The only line I would say I am unsure about is this one:
"Give the user permissions: `chown -R recipes:www-data /var/www/recipes`"
As I am not sure whether these permissions are necessary for this to work.
Hope this is useful, let me know if I can make further improvements.
My understanding is if you want to access the app on port 3000, you
would use `docker run -d -p 3000:8080 ...` for a Docker command. For
Docker Compose, it's:
```
nginx_recipes:
ports:
- 3000:80
```
Not having the backslashes for the `docker run` command resulted in an
error.
Using `80:80` is ignored. While it will work on port 80, it fails when
using any other port such as `3000:80`. Using `3000:8080` works.
Volumes should have a colon on the end, otherwise you get a `ERROR:
yaml.scanner.ScannerError: mapping values are not allowed here`
That said, the new Docker install isn't working for me yet, but I love
the idea of bundling the nginx files with the recipes container.
