I also agree with separate repositories per app. My web2py folder is a mercurial repository (I cloned the web2py repository http://code.google.com/p/web2py/source/checkout) Then for each application I want to make, I create a new repository for that application in the web2py/applications folder. So you end up with a nested repository structure but they actually play nicely and don't interfere with each other (thanks to the ignore files)
This way I can update web2py as needed to get new versions or bug fixes. And my applications are in separate repositories because they really have nothing to do with web2py core. On Wednesday, February 19, 2014 6:00:37 AM UTC-5, Tim Richardson wrote: > Well, I'm not very sophisticated but I have separate git repositories per > app, I can't any advantages in having one repository for everything. > > On Wednesday, 19 February 2014 12:13:13 UTC+11, Carlos Zenteno wrote: >> >> Do you guys version control just the /applications directory or the whole >> web2py tree? >> >> What is better for auto-deployment when pushing to the production repo? >> >> Thanks... >> > -- 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/groups/opt_out.
