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?

Thanks.

-Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to