On Wed, May 20, 2009 at 02:28:52PM +0100, Chris Withers wrote: > - which bits of a Pylons project do you version control? *
I version control anything that isn't automatically regenerated. That includes the Paster templates and boilerplate code (since it's rarely boilerplate when I'm done!) > - how do you build all the other bits? * I push my releases to a git repository that is accessible from my production server where I checkout and build an egg in the production virtualenv. For a long time, I built out of my working directly, but a recent feature mis-merge broke me of that bad habit :). > - what do people use to serve their sites? Is whatever > "paster serve blah.ini" using suitable for serving to the wide world > or does it need to be proxied through something like Apache? > > - if using "paster serve", how do people wire it so that it starts at > machine startup and stops at machine shutdown? > > - is "paster serve" the recommended option? If not, what is? I'd say I seem to be in the minority, based on the discussions here, but I use Apache+FastCGI. Never have any deployment problems. I restart Apache when I deploy a new version, which might annoy some people (I could kill my fcgi processes, but just don't usually bother). I do try to be the first hit so I see the initial load time! > * I'd like to be using buildout for things wherever possible, the > following is what I have so far: I have not used buildout, so I can't really comment. -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
