Mat Schaffer on 6 Oct 2007 23:44:53 -0000

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PhillyOnRails] SVN question

  • From: Mat Schaffer <>
  • To:
  • Subject: Re: [PhillyOnRails] SVN question
  • Date: Sat, 6 Oct 2007 19:44:38 -0400
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; bh=pEjp46ZhMmV1UenyfcMKmC7vn51sCMYgx68K5GJnXdY=; b=uo2Mc/LeGOpiqHhnbLPuZn7AT9GlPJEOuWClZ6lMFZMeT8xWbiKsMiGt9Xm+sNuIySnP5AnNaEsN9qvsJAnxloS8MLdjJAYej92oAsRB/6enRs3BMt2i60IDP5wt/3+OCe5vKwRKETCHsP89RH0V9DbwRVHtCuOJDxzyNMnCH/0=
  • List-archive: <>
  • Reply-to:
  • Sender:

On Oct 5, 2007, at 9:38 PM, Walter Lee Davis wrote:
I am just getting started with svn, and one thing that wondered as I am pondering the import of a gigantic project is what can I do to keep people from seeing the password to my server when it appears in my conf files? How do you keep something in version control, yet have sensitive information redacted at the same time?

As for keeping sensitive information version controlled, you could consider a separate repository. But in terms of handling things like database config files that are going to change from server to server you might want to take a look at the advice here:

You could potentially keep the production files under version control in a separate repository, then pull them in as part of the deployment procedure. But I think for most people, a version-controlled template does the trick. Kinda like what Randy said.
To unsubscribe or change your settings, visit: