{"thread":{"id":"20400","subject":"Advice needed - handling configuration files","startedAt":"2009-08-05T11:35:38Z","lastAt":"2009-08-05T11:35:38Z","messageCount":1,"participants":["Ian Hobson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"119607","messageId":"4A796E8A.70407@ianhobson.co.uk","threadId":"20400","inReplyTo":null,"subject":"Advice needed - handling configuration files","fromName":"Ian Hobson","fromEmail":"ian@ianhobson.co.uk","sentAt":"2009-08-05T11:35:38Z","receivedAt":"2009-08-05T11:35:38Z","isPatch":false,"sender":{"key":"ian@ianhobson.co.uk","avatar":null},"body":"Hi all,\n\nGit newbie here, so please spell things out.  I've been reading the docs \nand got quite confused  :)\n\nI have a web application that has been developed for one customer. It \nis  just about to go to three customers -each will need their own config \nfile, css file and directory of images. Each customer may have a test \nand production version that differ only in the config file. The \ndeveloper (me) also needs configuration files for various purposes \n(scripted testing and manual testing).\n\nWhat is the best way of handling this situation, so that the config, css \nand image files are under version control, without having to repeat \nchanges in  three branches?\n\nIf a patch set could be created that contained all but the changes to \nthe configuration files, then that could be pulled up into the \nmothership, and each satellite can have its own configuration. I want to \navoid renaming/copying files if possible because that is change that \ngoes into production untested.\n\nRegards\n\nIan\n"}]}