I can make a version for production use (in a week or two), for your critics.
For example, based on Appache wsgi. PS: maybe it is also worth to make a docker image for testing changes in Django source? On Wednesday, February 27, 2019 at 4:31:17 PM UTC+2, Jamesie Pic wrote: > > > most people currently lean towards a microservice architecture and > therefore towards flask. > "according to the 2018 JetBrains Developer Survey" and some people. > Why start a project with flask in 2019 instead of Quart which or > Starlette is another question that I suppose is out of the scope of > this mailing list. > > Anyway, the point of Docker is to build your own image that supports > both development and production given different runtime parameters. > The agile practice with docker is to build your immutable image in CI, > test it, deploy it to staging, have on-click deployment to production. > > The security and best practice documentation from docker are indeed a > lot to grasp, and beginners will most of the time start making > insecure (running as root) and inefficient (fat) images. Therefore for > their security Django might want to document making a docker file, > perhaps based on the alpine image that's the most lightweight. > > -- > ∞ > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f07ad32e-e74f-4cd3-945a-ed92692c2209%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
