If you’re not a developer, feel free to skip this post. 🙂
I’ve been re-organizing my SVN repositories over the last week or so. This is what I’ve finally come up:
- clients – all client projects live in here, with a sub-dir for each client.
- documentation – docs for Tasks Pro™, Tasks™, etc. Having them all under one repo makes sense as I often need to merge changes to PHP Doc System or the doc content between products.
- open-source – with a dir for each project, I’ll be able to open up anonymous SVN read access easily with them all in one place.
- personal – browser bookmarks, misc. application meta-data, etc. that I pull down to multiple machines.
- projects – smaller projects that don’t need their own repositories.
- web-sites – all of the sites I run are in SVN these days.
The goal is to allow some separation and organization of the various repos, but also allow me to merge changes across similar codebases and projects as needed.
Please post your suggestions, tips, “I do it this way” comments, etc. in the comments.
This post is part of the thread: Version Control – an ongoing story on this site. View the thread timeline for more context on this post.
what are you using for an SVN server alex?
I’m moving things over to TextDrive.
How do you handle WordPress in your repositories? Or you download WP in the old fashion way? (i.e. not from SVN)
I use svn:externals in projects that use WordPress.
I’m curious as well – trying to figure out whether setting one up would be worth my while, over just a nightly backup.
Quick question: did you consider a single repository, with each of those six categories represented by folders? I wonder about the pros/cons of the two approaches…
I’m sure it would be very useful for me as far as I’ve heard but couldn’t give it a try up to now. It looks very complicated.
A couple of reasons I didn’t do that:
1. I thought it would become too unweildy.
2. It would be more complicated to set up anonymous read access to the open-source folder in the single repo than it would to just open up the entire open-source repo.
I’m curious to know what kind of repository layout you’ve chosen. Assuming you use the trunk/tags/branches structure, did you choose to re-create that layout for EACH project, or does each project fall under one trunk,tag,branch directory?
Hope my question makes sense…
Each project has its own trunk/branches/tags structure.