I have given this issue a bit more thought, and it seems using Docker might be a bit too complex for the "just completed tutorial use case". Docker is nice, but if things do not work out the way you want, troubleshooting can get a bit complex.
Instead it might be good to *fully* document how to set up a virtual machine based Django setup. The documentation should include: - minimal information about how to install virtualbox and Ubuntu 14.04 image. (Maybe vagrant would be a better idea?) - how to setup Django with Gunicorn (is supervisord a good idea for process management?) - static files - media files - security - logging - multiple environments (for example, how to use settings for multiple environments. environment variables are the way to go IMO) - automatic deployment - backup, restore, clone production to qa (clone to qa is a really useful feature if your database is small enough for it) Second step would be to automate as much of the above list as possible. Maybe the mezzanine fab file is enough for that. The above list also tells a pretty good story about why I pursue a documented way to fully set up Django. When setting up a small Django app, doing all of the above things properly requires just too much effort. - Anssi -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c6bd553e-f21e-4a4f-ba5a-150e58bac0db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
