Docker compose environment uses django development server

[jkpr]

At our company we are thinking of running an instance of wooey to make our python scripts available to others. I noticed that it is the django development server running. So far so good, but I'm wondering how much it would take to stress out the server.

Could I recommend gunicorn?
https://docs.djangoproject.com/en/3.0/howto/deployment/wsgi/gunicorn/

[Chris7]

Sure. I wouldn't want the default to use gunicorn though, as the docker-compose is setup to really be a dev environment (but you can easily modify it to suit a more prod setup).

[jkpr]

Do you want docker-compose to be just for a dev setup? I was attracted to this project as a way to setup a quick/easy website for others to use.

Are you interested in something like this: https://docs.docker.com/compose/extends/#multiple-compose-files
and having an override file such as docker-compose.prod.yml ?

[Chris7]

Wooey's docker-compose was really meant for a dev setup. It is pretty far from a prod setup that gunicorn wouldn't address, like having a persistant database that isn't postgres + volume.

If you want to submit a PR with your ideas, then more than willing to take a look at it, but I'm not sure how comfortable I am with users having a "production" docker-compose file that is missing so many other parts of a production deployment.

[Chris7]

Looking at #321, one thing I do think would be very useful is a simple docker-compose text users can copy that uses the dockerhub image and doesn't require cloning this repo.