[eluser]Gordaen[/eluser]
After reading quite a bit about CI, I've decided to give it a try. I'm halfway through redesigning a site, so I figured now is a good time to make the changes. I have a few questions before I get too far though.
I read a few past posts about running multiple sites/applications through CI, and I think I have decided to do mine this way:
/ci_path/application/sitename-dev/
/ci_path/application/sitename-live/
Obviously there will be quite a bit of overlap between the two, but it feels "safer" to keep the development site as a separate application. That way I can be as experimental as I want without too much worry. If everything is good on the dev site, I can copy over the appropriate libraries, views, etc. The naming convention should also make it clear/easy if I decide to modify more of my sites to use CI. Does that make sense?
Would it be best to create additional separate paths for logs, cache, etc. in order to help keep the sites separate? e.g., $config['log_path'] = '/ci_path/logs/sitename-dev/';
Is there any logical way of tying subversion in with all of this? Right now, the site is in a svn repository. I work on the dev site until everything is good and check in the changes. Then I just do an "svn up" on the live site. The way I have it now, however, is that a "settings.php" file is loaded that configures various settings (e.g., logging, database info, etc.). With CI, it makes more sense to just have the appropriate info in each "site's" config file, which would mean I obviously would not include that in the svn repository (unless I used svn hooks, but that's getting away from the simplicity I am going for). Does it make sense to use svn and just be very selective about which files are in the repository, or would it be better to have an auto-loaded config file, or some other option? I don't
have to use subversion, I just find it extremely useful.
That's it for now. Thanks for reading such a long (and possibly rambling) first post
