steve cooley presents

So I’ve been using and enjoying subversion for many months now. I think there are a lot of things that I don’t use, but I still find it immensely helpful in my day to day work. Up until recently, I’ve been using it locally, so that would be “file:///” instead of “svn://” But now I have a need to set up SVN as a server, so I’ve been trying to parse through the instructions, and it seems almost too easy. You edit the “passwd” and “authz” files in the “conf” folder, annnnd… pliff.. nothing happens. You can’t check stuff in. So I was starting to doubt SVN as a viable tool for this project because I just couldn’t get it to work, and… I need to get past this stupid step and get on to getting things done.

And then Homg, I just figured out what this guy said:

> Any suggestions out there?

Look at the conf/svnserve.conf file in your repository, it defaults to
allowing only read-only access, to get write access you'll either need
to turn on anonymous writes, like this:

[general]
anon-access = write

Or you'll have to configure a password database, as described in the
file's comments.

-garrett

So there’s *ONE CHARACTER* that you have to delete from the “svnserve.conf” file. The pound character “#” in front of the line that is this:

# password-db = passwd

so that it (comically, at this point) reads:

password-db = passwd

I feel like this should have been more obvious, but I don’t know how it could have been more obvious. It just wasn’t for some reason.

Technorati Tags: svnserve, subversion, svn

Related items

• remembering how to paint, part 3
• remembering how to paint, part 2
• remembering how to paint
• 2008 Auction Info
• the arduino project box project has begun