Yes. I have one checkout that I always keep at the latest version. Its easy since I just clone the tagged revisions from mercurial. I simlink all of my applications to this single web2py instance.
If I need to work on web2py, I clone a brand new repository from tip and then begin working. If I need to test an app, its as easy as making another simlink to this folder. For changes, I don't commit anything, but just run an ``hg diff >> patchname.diff`` and then send that to Massimo. Usually he reviews the patches in detail and will make sure none of the changes break things (like print statements) and then he commits them into trunk. For developement, I do not use routes, this allows me to have 15 apps on the same web2py base code. For production I always use a separate web2py install for each site and a routes.py for that site (which I store in myapp/private and copy over to the web2py folder when deploying) I kind of have the following layout ~/Applications/web2py/ # this is the stable branch ~/Applications/web2py-dev/ # this is a fresh branch I use for contributions ~/Applications/web2py*/applications/ # all apps are simlinked here. ~/Workspace/Web/ # Folders for each of my web2py apps. These are the folders that contain models controllers views etc.. -- Thadeus On Mon, Aug 9, 2010 at 1:14 PM, Michael Wolfe <[email protected]> wrote: > nted to make sure my design decisions would
