|
Monday 16 June 2008 1:32:28 am
In a comment (http://ez.no/developer/articles/using_subversion_with_ez_publish/how_can_i_use_my_own_ini_settings), Gaetano Giunta offers a helpful suggestion for managing different ini files for development, testing, and production. But could someone clarify how one goes about copying the changes to be applied the testing branch, for example? I'm running into this problem: 1. Make the change in my own settings/testing/siteaccess/myaccess/site.ini.append.php. 2. Commit the changes. 3. Try to svn copy settings/testing to settings (in the testing branch), so it will easily overwrite my development settings for site.ini. However, I get an error saying the path already exists. What's the simplest way of handling this--preferably without having to duplicate design.ini and other ini files which can be identical in development, testing, and production?
Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog
|
