This article showing you how to deploy a secure and manageable Subversion installation that uses Apache 2.0 as a central authentication checkpoint.
Setting Up Subversion for One or Multiple Projects
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
The article instructs to compile Apache from source. What is this, LFS? I can’t think of a single distribution that does not provide Apache packages. The only thing to gain from compiling from source is wasted time and the risk of a security flaw due to not staying on top of packages that would be updated by the distribution. Not to mention the lack of package management and versioning.
Stupid.
“I can’t think of a single distribution that does not provide Apache packages.”
providing custom options not provided within the package. it might be more useful to change the srpm or USE variable or something like that thou
Ummm….How about OpenBSD?
It is not that stupid. I run subversions on some somewhat old
distros, what is installed on them works, and I see no reason
to upgrade the distro. They don’t ship apache2 though, so compiling apache from source was required. And rather easy as well
Does it matter that it was *his* prefered method of installation???
Aside form the source install, did you gain anything? Or are we just picking holes?
Thanks for the article as I am about to setup a subversion server and the info within the article was useful.
And now a tut to setting it up on Win32 would be nice. Seriously.
“Win32 and security” jokes in 3…2…1
I second that. With local and remote, sans apache if possible (maybe through iis?).
Assuming you mean OpenBSD doesn’t have an Apache package; it does. In fact, it is installed for you by default.
If that’s not what you meant, then forget I even mentioned it.
Anyone know whether the issue of svn repository needing repair every now and then is fixed already? Or are they going to fix it?
The repository seems to break almost every time I do svn+ssh access from a Windows box, which uses openssh from cygwin and (obviously) fails to perform every now and then. Next time I access the repository, I need to run svnadmin repair on it.
This would not look good if I had just advcocated adoption of svn in corporate settings (luckily, I haven’t)… the breakage should really be fixed.
This is not a but, but more a permission problem with resetting the permissions.
What happens is that the permissions are altered by different users doing ssh access, there are various ways to fix this and there is a specific entry in the subversion docs as well as in the faq about this problem.
As far as I can see it is not fixable from the subversion side since it is not really a bug.
>Assuming you mean OpenBSD doesn’t have an Apache package; it >does. In fact, it is installed for you by default.
And it comes with 1.3.x , Subversion only supports the latest
2.0.x versions
The subversion docs indicate that you can use a stand alone server that ships with subversion, though they seem to indicate it’s only appropriate for smaller installs.
http://svnbook.red-bean.com/svnbook/ch06.html