On Friday, July 22, 2016 at 4:45:58 AM UTC-7, Alex Santana wrote: > > Thanks Dave, > > I was doing exactly this! >
I spent some time prototyping a fabfile to use when a new release comes out, so I've poked around some of these issues. I did forget to mention that if you have some custom static files, like favicons, those should copy just fine. Custom css and js files probably copy, but may need extra testing, and the change from Bootstrap 2 to 3 changed some things like nested menus. /dps > On Thursday, July 21, 2016 at 7:50:24 PM UTC+2, Dave S wrote: >> >> >> On Thursday, July 21, 2016 at 9:02:57 AM UTC-7, Alex Santana wrote: >> >> >>> Now I need to realize how to migrate my applications to the git version. >>> >> >> It's mostly a matter of copying the controllers, models, and modules you >> have. If you have language files, copy those. If you have an >> application-level routes.py, that will probably copy. If your database is >> SQLite (okay for development and lightly used sites), then you may want to >> export that data. For other engines, you can probably just reuse the >> connection string. The old app probably used models/db.py to set up >> configuration data, but now you can used appconfig (makes your code more >> portable if you change server environments or between dev and production); >> look at the welcome app to see how that is done. >> >> /dps >> >> -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
