It really depends on your use case. I've deployed production Web2py on dedicated server, Heroku, and now AWS Lambda (Serverless). Heroku gives you the best metrics and ops, but If I had to do it again, I would do them all on AWS Lambda due to the reduced cost during down time and the auto-scaling during spikes.
On Monday, December 3, 2018 at 10:37:01 AM UTC-6, VP wrote: > > Hello Web2py users/developers, > > I haven't used Web2py for a while, but I'm contemplating to use it for the > next project (with Python 3). What deployment setup would you recommend? > I'm looking for a simple Linux-based solution (my own server) that is easy > to set up, reliable, hopefully maintenance-free. Years ago, I set up > web2py with Apache, Nginx for various projects, but it's been a while. I > am wondering what the best options are these days. > > By the way, I'm glad to still see web2py still around. I remember the > days when people lambasted web2py for various "un-Pythonic design > decisions". There were dozens of web-frameworks back then. Today, Django, > Flask and Web2py co-exist pretty well. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
