NYCPHP Meetup

[y2rob at aol.com]

no, i wasn't trying to criticize, i just wasn't following how your app was configured.? it makes sense though. i've seen it done in both ways, it mostly is determine how you want your application distributed.

~rob


 

-----Original Message-----
From: Chris Snyder <chsnyder at gmail.com>
To: NYPHP Talk <talk at lists.nyphp.org>
Sent: Mon, 30 Mar 2009 12:19 pm
Subject: Re: [nycphp-talk] git to this presentation










2009/3/30  <y2rob at aol.com>:
> i think you do bring up some interesting points, but i'm confused on the
> sensitive material part.? do you not have this in your version control?? i
> would assume you have a check to determine if you're developing locally,
> staging or production, so that you're not editing these files per server.
>
> ~rob

I was actually talking about /etc configuration files that really are
local, and not part of any php project.

In php projects, we normally create config.php-dist as a prototype
without any passwords or keys, and include that in the repository.
Then we save it as config.php locally. The config.php never gets
checked into the repository as it is unique to each installation.

I'm sure there are slicker ways to handle that, but it's always worked
just fine.
_______________________________________________
New York PHP User Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk

http://www.nyphp.org/show_participation.php



 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20090330/1244a375/attachment.html>