Why would you ignore your *.ini files. I keep mine versioned so they are easily tracked and updated with deployment. I generally follow the same steps described above. My server deployment is a little different. I check out into a different directory on the server then rsync the changes over into the application directory. The account that checks out from svn is read only.
I do it this way for a couple of reasons. You won't have problems with doing dev on your server causing svn conflicts on your machines. The rsync will just wipe out all test changes that you have made. The reason its read only is it removes most of the temptation to make changes locally. If you needed to test a quick change then you would scp the file in directly. Also, it keeps the version control history honest for who made what changes. On Mon, Oct 5, 2009 at 12:05 PM, Mike Orr <[email protected]> wrote: > > On Oct 5, 9:27 am, Dan06 <[email protected]> wrote: > >> On Oct 3, 6:39 pm, Mike Orr <[email protected]> wrote: > >> > >> > I don't understand the difference between your approaches. > >> > >> The difference (and the question) is whether on the (pylons) > >> development server should there be both the original pylons project > >> directory AND the checked out pylons project from the repository or > >> just the checked out pylons project. > >> > >> From your response, it seems like you use only the checked out pylons > >> project. > > > Yes. The original directory won't be needed again. > > > On Mon, Oct 5, 2009 at 10:46 AM, Wyatt Lee Baldwin > <[email protected]> wrote: > > > A typical thing to do would be to... > > > > 1) Create a new Pylons project on your local machine (or dev server or > > wherever), > > 2) Immediately import the project into Subversion (minus some cruft--I > > think there may be a guide for this somewhere), > > 3) Check out the project from Subversion. > > 4) Move the original project directory (generated by paster) into the > > trash. > > 5) Make all your changes in the working copy created in step 3. > > I do essentially the same thing but slightly differently. > > 1) Create the application outside Subversion. > 2) Move it into Subversion. > 3) Delete stuff I'll never user (public/index.html and its images). > 4) "svn add" everything except the egg-info directory. > 5) Set the svn:ignore properties the way I like them (*.pyc, data, > *.ini, myapp.egg-info). > 6) Commit. > 7) Make initial changes such as commenting out StatusCodeRedirect in > middleware.py (I prefer simple error pages). These are changes I do > the same in every application. > 8) Commit again. > 9) Start adding my controllers and routes. > > The reason for creating the application outside Subversion is that > Paster has a built-in feature that automatically "svn add"'s the files > if it's under Subversion (not sure if it commits them too?), but I > think it's overzealous. It adds the egg-info files, for instance, > which are changed every time you install the app and are specific to > the computer. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
