I'm trying to implement subversion to control the versioning of our website.
I think i have read enough to make myself dangerous.
Here is a simplified example of what i want to do.
So what I want to do is have a repository for "core" which would be the root
and style folders, then department is it's own repository, and committees
it's own. Is it possible to make this work. I have all the parts of the site
My need is to get the 2+ gig of data into subversion. I haven't had a
successful import. It has complained about file sizes, and other times i
have gotten connection reset by host and various other things. So i kept
looking for solutions. I found information on svn:external but haven't
gotten it to work as i want. I can't find a way to use svn:externals such
that if i want to check out 'departments' it will download the department
files into the department folder, and the 'core' files are put into the
parent of that folder. Is this possible?
I don't mind if changes to core are not committed back in, i just don't want
to have department having a different set of 'core' files from committees. A
simple copy of core would be fine as long as it is the current version.
Changes to these "core" files will be their own project.
Is this even worth the effort to try and make work? The way I see this as
working is i don't need to work with all 2 gig of the site. There is a lot
of static content in some directories that I don't need to carry around on
my laptop, but needs to be preserved. I have visions of moving this content
out of the structure and using apache to alias it back into place. Because
of the amount of work this would be a great situation for me to start making
small changes with subversion until i have taken care of them all.
If i could create a script that is something to the extent of "checkout the
repository, but exclude /department /committee and /jobs" that would work
Any direction would be appreciated.
Received on Tue Mar 27 04:34:32 2007