I am trying to set up a centralised workflow using bzr as VCS with multiple developers. My problem is now, that all of the developers have to push via ssh to a centralised repo which also serves a the host for the web application.

I have several config files which I do not want to push to the repo, because I do not want to override them. I tried to set them up properly once, then I altered them locally to run the application on my machine. I thought I could then just remove --keep them and set them to ignore.

However, everytime I push now bzr removes those files from the repo... Is there any way to include those files from versioning and still transfer them everytime I push?

link|improve this question
feedback

1 Answer

Meanwhile I talked to the guys of bzr over at Launchpad and they told me that there is currently no way to keep ignored files when pushing. Maybe they'll add this feature in the future. It is also possible to use filtered views, which will be introduced in 2.5.

My solution was to read the $_ENV variable as my provider kindly places an unique id there for every web application we use. On my local machine, this $_ENV key/value is not set and therefor other seetings are loaded.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.