Developing with SVN and CI - best practices?

[eluser]Phil Sturgeon[/eluser]
Config
Much of this can be kept the same while working through it all. You can set the basic config stuff that wont change using some sneaky plain PHP in the config files, for example:

Code:

if($_SERVER['SERVER_NAME'] == 'localhost'):
    $config['base_url']    = "http://localhost/project/";
else:
    $config['base_url']    = "http://beta.project.com/";
endif;

You could perhaps even do that in a few other places in the config file, then just remember to remove it all when the project is complete.

OR you can simply commit the server config settings, change your copy to settings that work for your machine then use SVN's ignore to make sure the changes are not commited.


Database
I use two online databases, live and test. All my team work on the test one (which is online ofc) but we keep a .sql file in the trunk just to make sure we have a backup of the DB in case we lose it or our internet randomly breaks, then we can grab the .sql file and run our DB locally.


Large Files
Upload to FTP somewhere and post a file with a link to them in the trunk. That way if the files move you can track where they have moved, and all your team know where they are without clogging your SVN.