I thought I asked this question before, but now I can’t find it! Maybe I
didn’t succesfully navigate a capcha or something. So I’ll try again and
try to make the question simpler and more concise.
Let’s say I have an open source Rails project, being collaboratively
worked on by several developers at several different sites/institutions.
We have a common SVN for the code, of course.
But there are a few config files that are not common. databases.yml,
perhaps environment.rb, perhaps even some fixtures. In my case, I have
unusual other files that are not common, say some stuff in the directory
app/layouts/local. But this could apply even just to the standard Rails
Individual developers at individual sites really want to keep those
'local’files in their own local svn—but still have the bulk of the
code in the main shared svn.
The fact that these files are scattered about the Rails hiearchy doesnt’
help–and the fact that some of them (ie databases.yml) are in a
directory that otherwise needs to be in the shared svn–makes it
Have other people been in this situation? What solutions do you use? How
do you handle this? Any advice would be welcome!
I am contemplating some horrible rake tasks that assemble all this
‘local’ stuff for you and import/co them from your local svn, but the
details seem terribly complex.