1. You do not need to byte compile form shell. The code is byte compiled when requested
2. bug can of worms. Problem in a multi-server environment is that only one of the server can do migrations at once but all need the correct .table files. I do not have a simple answer. Make sure you look into gluon/contrib/heroku.py On Thursday, 12 March 2015 09:02:54 UTC-5, Louis Amon wrote: > > I'm trying to create a Buildpack designed specifically for deploying > Web2py-based applications on Heroku. > > Buildpacks are shell programs that are used to build & deploy slugs on > Heroku. > The buildpack runs *before* the web2py application is launched. > > It is basically a kind of deploy hook. > > > The features I'd like to include in the web2py buildpack are : > > - Byte-compilation of the web2py application > - Migration and/or re-creation of the .table files > - Installation of pip dependencies > > This would allow automatic optimization of the run speed and tackle the > very tricky ephemeral filesystem of Heroku. > > > I could really use some insights about how I should go about building this. > > Specifically, I need to know: > > 1. how to to byte-compile directly from the shell or from a python > script > 2. what strategy I should use to handle migrations at deploy-time > > > This is the official buildpack for Python, which I intend to build mine > upon : https://github.com/heroku/heroku-buildpack-python > > This is the documentation for the Buildpack API provided by Heroku : > https://devcenter.heroku.com/articles/buildpack-api > > -- 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.
