Pat Farrell wrote:
> Parrish, Ken wrote:
>> 99.99% of what’s in our repository is just source code that everyone
>> needs. However there are a few files that contain production usernames,
>> passwords and other references to assets that we would like to encrypt
>> and allow access only to selected users or those with an encryption key.
>
> Its simple. put those things in a properties file or equivalent and do
> not use SVN for them.
>
> Your problem is more fundamental than whether or not SVN can do the
> specific things you want, rather, you should not want to do what you are
> thinking about.
>
> Keeping production server secrets is a separate topic.
That's correct in theory, but I'd bet that most places that keep any
production code/configurations in subversion have this issue. That is,
they either include things like the backend database credententials in
their version-controlled configurations when they shouldn't, or they
don't version-control the configurations or management scripts at all
when they should. There are just too many places where you can't
separate them.
--
Les Mikesell
lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402979
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-02 18:03:48 CEST