On Sat, Oct 3, 2009 at 11:26 AM, Dan06 <[email protected]> wrote: > > I'm curious as to what is standard/recommend practice when it comes to > pylons code version control with subversion. I've setup a server with > pylons and I currently use ssh to create the project, app, > controllers, etc.. Should I import the project into svn and then just > add each additional controller, view, etc. as I go? Or should I import > the code into svn, then checkout the project onto the same server so > any changes can be made via commits?
I don't understand the difference between your approaches. My department has a shared Subversion server. I have my Pylons repository checked out on my workstation, server, and backup server. (I have a staging server too, but it's being used for something else right now.) I do my work on my workstation, check it in, do "svn update" on the servers, and restart the Pylons application. This works pretty well except when I make a bugfix I want to test on the server before checking in. Usually I'm lazy and check it in and update, but then I have to repeatedly check the same thing in if it doesn't work on the server. So sometimes I scp the files over, make sure they work on the server, and then commit them from the server. That's more tedious because you have to type the full path for scp, but it keeps the repository cleaner. I prefer to check in a logical unit of work rather than each controller or template individually. That keeps actions and their configuration somewhat together. Another issue is how to arrange your branches. I have production in the trunk, old releases in a tags directory, and large renovations or experiments in a branches directory. That works well if you're making small updates continuously. If you put only numbered releases into production, you may want to use the trunk for development and put releases into branches. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
