First here's some context on what I want to achieve.
I'm writing a small Django application for basic project management, something like a simplified Google Code and I want tight SVN integration, which means that I want to be able to manage user access rights. I also want my application to create the repository when a project is created, just like Google Code does.
Now the problem:
I could serve a single repository and pile all my projects in a root folder (like I presently do) OR start a svnserve daemon for each repository.
I can't use the single server setup since all projects would be treated as one big project, making revision numbering borderline useless and per project rights management impossible (well, I think).
I've found this article which describes mostly what I was about to do:
http://articles.slicehost.com/2007/9/6/multiple-repositories-and-subversion
However my co-worker thinks it's an overkill and I shouldn't do it.
For myself, I think that considering that I will hardly ever go over 100 projects this is a non-issue. And even if I unrealistically had 500 active projects, the server would probably cope just fine with 500 idle processes.
Who's right?
Or should I go for something else, like Mercurial?