Comments on: An alternative to “hacking” config files

By: jzimmerman

jzimmerman — Tue, 19 Sep 2006 05:11:30 +0000

I develop locally on my laptop, have experimented with local svn version control, but since I am the only one working on my projects I usually just gzip my directories for backups.

I use rsync to deploy code changes to my servers though. I have 2 different database config files. database.php.live, database.php.local.

My script that runs rsync just moves files around before syncing.

Here is my script. I execute it from the command line….
————————————————————
#!/bin/bash
chmod -R 755 *
cp ./app/config/database.php.live ./app/config/database.php
rsync -az -e ssh –delete ./ username@example.com:/path/to/public/directory
cp ./app/config/database.php.local ./app/config/database.php
————————————————————

No logic in my project, just moving files around before and after syncing.

By: cakebaker

cakebaker — Mon, 18 Sep 2006 07:41:49 +0000

@Kjell Bublitz: I use a rather pragmatic approach. I just copy the folders I work with (controllers, models, views) to the “live” folder, synchronize the “live” folder with the repository and commit the changes.

By: Kjell Bublitz

Kjell Bublitz — Sun, 17 Sep 2006 01:21:29 +0000

And how do you manage to keep both of your SVN version in synch without overwriting the live config by accident? Some hints would be great. TIA

By: Felix Geisendörfer

Felix Geisendörfer — Sat, 16 Sep 2006 20:10:55 +0000

Well I can’t argue that that the SVN solution is pretty good, however, I like having this very straight forward method as well since some of the very small projects / code demonstration things I write are not managed via SVN.