Concerning Re: exclude files from checkout by
Tyler Roscoe wrote on 27 Jul 2009, 22:56, at least in part:
> On Tue, Jul 28, 2009 at 07:45:16AM +0200, Jan Hendrik wrote:
> > So while still wanting to have this php.ini under version control I
> > would like to have it checked out by default only in the working
> > copy used for final testing & upload to the hoster.
>
> I would just store the production php.ini elsewhere in the repo. Then
> I would use a script to set up the production environment (this is a
> wise thing to have scripted anyway, for various reasons). The script
> would take care of copying the php.ini into the working copy.
After finding out I have read access to the php.ini on the hosted
production server (expected only a server process would have) this
is definitely the way to go: load their php.ini, modify the values as
necessary, and save it into the production copy. No need to have
an actual php.ini anywhere in the repository/working copies where
it only would wind up being used in the development environment.
As they run PHP as FCGI while we use mod_php (after reading
dozens of articles I really don't know if the one or the other actually
is more or less secure, at least significantly) we can even save
copying it into all subfolders and just SetEnv in server root
.htaccess without compromising development/testing environments.
Thanks again.
JH
>
> tyler
---------------------------------------
Freedom quote:
We've been blessed with the opportunity to stand for something -
for liberty and freedom and fairness.
And these are things worth fighting for, worth devoting our lives to.
-- Ronald Reagan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376516
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-29 10:49:18 CEST