Hi Richard, I started at the command line, then built a bash script for quick cloning. I also use Web2py's built in versioning on the Mac, used Eclipse and a script that allows you to update a subdirectory full of projects. Now I mostly use the command line and batch pull and updates. One guy I develop with really likes fully configuring Eclipse using the voa-web2py2eclpse script but I find it slower and a much more complex system to maintain than I require for my needs at the moment (it does work nicely though once everything is setup).
http://code.google.com/p/uc-tools/ This project has the batch pull and update python script (mercurial_util.py) I like it a lot. Also included is a very basic bash script for cloning projects quickly, although it would need to be adjusted for project names that do not start with "uc_"). The python mercurial script rocks. http://code.google.com/p/voa-web2py2eclipse/ This project has a nice script for turning Web2py applications into Eclipse project. Warning, setup can be a really big dealif you are not a regular Eclipse user. Great for large projects, but I tend to avoid it cause I am in love with my text editor. Have Fun, Chris Voice of Access On Sep 22, 4:40 pm, Richard Vézina <[email protected]> wrote: > Hello, > > I would start using version control tool in my dev practice and I would like > to know what the "best" practice to adopt with web2py. > > There is not so much information in the book about the "versioning" tool > available into web2py. > > Also, I am not well experienced with the version control. > > I learn mercurial because it is planned to be the unique (can't find the > mail Massimo were saying it) version control that will be use in the future > of web2py... > > I wondering to know if it is better to manage a app with mercurial straight > (without the versioning tool of web2py) or with the w2p versioning tool? > > I would have this work pattern : > > Trunk = App > Branch = clone of trunk > App version = tagged trunk > > Thank you for your help. > > Richard
