Jason The whole point of me providing a docker image is to make it a 'best of breed' solution so people do not have to muck around having to configure everything themselves.
It uses mod_wsgi-express and so people do not need to worry about server configuration themselves. By suggesting using nginx in the same container when the pre configured setup will be more than adequate for 95+% of people sort of defeats the whole point of why the image was created. As to TLS, mod_wsgi-express already makes that easy. Static file serving is also more than adequate and mod_wsgi-express provides special configuration to allow special layering capabilities with the way that static file handling is done to make that easy as well. Finally, in a docker world, embedding nginx in the same container sort of goes against the philosophy of how you use containers. The approach one would use if there was some need to offload some work to nginx, especially if using it for load balancing, would be to have the nginx running in a different container which was linked to the containers running the Python web application. Anyway, I will followup with the TLS options and how to set it up in a while after have dumped kids at school. Graham On 11/05/2015, at 6:42 AM, Jason Garber <[email protected]> wrote: > I could be completely off base, but if you can run nginx in that container it > solves 3 important issues: > > 1. Slow client buffering > 2. TLS is super easy > 3. Static asset serving is blazing fast > > I can provide configs if desired... > > On May 10, 2015 4:39 PM, "Michael Blake" <[email protected]> wrote: > Works flawlessly. I added a few pre-build commands, and my Flask app starts > right up on port 80 of the container, and it runs... fast! Definitely > production grade (at least for my purposes). > > The next step I need is to setup TLS on the site, and a few redirects. I'm > poking around in the .whiskey/apache area to see where to add in the config, > but it's not immediately apparent where, or correct way to add the necessary > SSLCertificate / rewrite directives. I checked over the docs and was looking > for more about the .whiskey folder, and how that is setup. > > Any help is appreciated, thanks! > > Mike > > On Wednesday, November 26, 2014 at 6:20:13 AM UTC-5, Graham Dumpleton wrote: > If anyone is a user of docker and/or has already been playing around with > mod_wsgi-express, you might like to monitor my latest little project. > > https://registry.hub.docker.com/u/grahamdumpleton/mod-wsgi-docker/ > > Hard to see how one could make it simpler. > > Graham > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
