Sensitive Information in SVN

[Carl Forde]

One common way of dealing with this situation is to have a 'sample'
configuration file and omit a real configuration file. As part of the
installation the sample file is copied to the real location eg. 'cp
fluid.conf.sample fluid.conf' and then edit the real file to have the
right values. This way the real configuration is never in svn and so
avoids all these issues. If you want, you can get fancy and have the
system detect the missing configuration file and provide a nice
interface to create one....

Carl

On Mon, Feb 2, 2009 at 12:44 PM, electBlake <electblake at gmail.com> wrote:
> Hello Hello,
>
> Hope everyone's weekend was swell and I hope that people stopped playing
> with their computers for at least 15 minutes to enjoy the nice day we had on
> sunday (torontians - I'm looking at you)
>
> anyway...
>
> I'm moving my progress with CakePHP into the system bit by bit now and I
> realized that maybe... I don't want to commit some configuration files that
> contain sensitive information (for instance database connection info)
>
> Should I leave it out and write instructions on getting it configured?
> Becuase as I udnerstand it you should be able to co a working copy of the
> site and have it run on your own system/environment.
>
> Any ideas? (I'm going to leave it out for now, but I'm curious how svn'ers
> handle this type of situation)
>
> - Blake
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>



-- 
Start by doing what's necessary;
then do what's possible;
and suddenly you are doing the impossible.
-- Saint Francis of Assisi