for models, it's as easy as using a single file called models/0_connection.py that holds the "customizable bits" (e.g. the DAL connection string) and using a models/db.py for your "static things", i.e. your define_tables statements.
For updates to views that they customized in the meantime and you changed in the upgrade, it's not a simple task...everything that you change may (or not) collide with their own customizations. On Monday, June 24, 2013 7:56:47 PM UTC+2, pa...@cancamusa.net wrote: > > How do you guys release upgrades of your own apps? > > The setup is: > > - You write a web2py app and release the code. > - Several people install it on their servers. > - They change the database connection string, and little more. It works > for real. > - Over time, they customize css files, even some views. > - You write non-radical updates for your web2py app, but that includes > models, controllers, views, and static js and css files. > > Now you want them to install the new code, but they have to update the one > line in db.py that connects to the database, and they want to keep their > data, logos, css, and views. > > I didn't find a standard place in the book for this. > > Thanks for your ideas/suggestions > -- --- 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/groups/opt_out.
