The way you describe the environment, it's impossible to bring
deterministic automated updates. If you have users customizing views, css,
etc., there is bound to be some manual intervention needed if your updates
also include views, css, etc.
You could use git, mercurial or a similar tool, but
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
This sounds a lot like the reason shared version control was invented,
which provides tools to manage simultaneous development on the same code
base. This is actually how web2py is developed, although of course with the
expectation that changes will be merged.
Look at github.
--
---
You
I was looking at comparisons of such websites, but I though that must
be a common issue fo web2py developers, so that's why I asked. I can
design the app in such a way that this problem does not arise, but it
would take more work and I would be wasting the great admin interface.
My time is
web2py uses github and/or google code, developer's choice.
--
---
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
5 matches
Mail list logo
