This nginx config file doesn't look specific for docker.
Why is it in this subdir and why is it named pokeapi.conf?
These numbers in gunicorn.py.ini seem a little bit random.
And @phalt why is wsgiref==0.1.2 a dependency wsgiref is since py2.5 in the standardlib and the pypi version seems not to be python3 compatible.

pokeapi.conf is added to the nginx container on docker build. The configuration is adapted to proxy the requests to the app container, I don't understand how it should be more specific to docker.

And the gunicorn configuration is from the docs: http://docs.gunicorn.org/en/latest/configure.html#configuration-file

The question was why it is in this subdir (docker/) though not be docker specific.
It could be somewhere else named nginx.conf and everyone should see that this is a nginx config file not specific to docker.
After the docs max_requests is to limit the damage of memory leaks (should be not needed if there are no memory leaks) and not set in the config you linked.

True, I'll move it elsewhere. But as app is hardcoded in the config file, I don't think you can use it easily in a classic nginx installation (ie. you'll have to edit the hosts file to point app to localhost)

@nimaje on the wsgiref - I've not updated the dependencies in a while. These are the pip freeze results from way back when I was building it.

@ThisIsAreku looks super good. What's the purpose of this vs the development version that we have in docker?

This version is more oriented to production system, with a proper isolation between services. Also, (IMO) it's easier to manage an application with docker-compose, you don't have to configure manually your server.

Okay, I really wanna merge this! 👍 Let's get another person to check it off first

👍