Keeping local configuration versioned

[Matthew D. Fuller]

On Thu, Nov 27, 2008 at 12:27:55PM +0000 I heard the voice of
Maciej Katafiasz, and lo! it spake thus:
> 
> I'm looking for a solution to what I think is a fairly common
> problem: I'm working on a website, and obviously have a local
> branch. This branch, in addition to all the development I want to
> push upstream, has some changes related to the DB/host settings that
> I _don't_ want propagated into mainline, but which I'd nevertheless
> like to have versioned

I do roughly this all day every day.  And I just do it by having a
live.conf.php and dev.conf.php, and have all the code just
include("conf.php"), which is an unversioned and .bzignore'd symlink
to whichever is appropriate in a given case (or indeed, a symlink to
neither and to a third which is appropriate in other special cases,
and doesn't get versioned).

On the deployed codebases, the symlinks are automatically managed via
the Makefiles I use to deploy, but you could automate them some other
way, or just set them up manually once since they wouldn't need to be
touched again on deployed versions.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.