my svn tags/trunk/branches look like this: /config
/web /web/www.site.com/ /web/other.site.com/ /web-pylons /web-pylons/apps then i use symlinks to make more sense ie-- the public folder in pylons app has symlinks for _img _js _css to the dirs in /web/www.site.com/DIR -- this way designers and front-end folks can work on that , along with static files. using the same strategy, in /config i have different deployment setups... one for staging , production, and a base developer and any others... and .ini for pylons, nginx, solr, apache, etc are all archived and versioned in there. the only difference between the two, is that i DO version control the symlinks for the content stuff (it never changes), and I DONT version control the config symlinks sometimes i get nerdy and have a python script install the correct symlinks for each environment. but usually i just do it manually. i find this approach really really really useful. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
