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.
Thanks, Tyler. While the actual production copy is more or less
out of reach (hosted webspace) with little to set up for me it still
might work by having a cron script on the hosted server to either
propagate symlinks to php.ini into any folder with *.php files or to
modify .htaccess by adding a SetEnv line. The pitfall is that the
configurations of our local test area and those defined by that
php.ini may get apart over time. Yet activating it in the test area
will have it end up in the development working copies, too, rather
sooner than later since minor stuff is done and committed directly
from the test area (e.g. typos). Having some way to label items in
the repository to be ignored on normal checkout/update except
when purposely requested would eliminate this. Guess I have to
give this scripting of test/production environment some more
thoughts.
JH
---------------------------------------
Freedom quote:
The ultimate test of a belief in free speech
should be whether it can be extended to people you hate.
-- Justice Oliver Wendell Holmes
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376274
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-28 14:49:20 CEST