tortoisesvn - Manage config file differences between development and production servers with SVN -
i have few files of .net app different in production server development server. example:
- web.config
- masterpage.master
- account/account.aspx
- blog/web.config
- and few more...
what best way manage these differences svn? i've heard maintaining config folder in trunk creating branch "different" files, merging them release tag.
i use svn trunk main development (stable) , tag trunk when it's ready released. trunk deploys development server , release tag deploys production server via ftp.
one possibility leave build/deploy process.
so, web.config have following in svn: web.config (this can development version) web.config.qa (if have qa environment) web.config.prod
at build/deploy time, deployment process "knows" environment deploying (based on control - environment variables, script parameters, etc), , substitutes correct config file in place.
i prefer method because leaves directory , file structure intact (vs. having config folder), avoiding unnecessary branches , merging pains. require diligence in ensuring files updated when changes made aren't environment specific, going pay price regardless of strategy.
Comments
Post a Comment