Hello Jukka,

Jukka Zitting wrote:
Hi,

On Mon, Feb 9, 2009 at 4:42 PM, Ceki Gulcu <c...@qos.ch> wrote:
I guess that you'd "svnsync initialize" both repositories with a username
and password of your choice and we'd proceed from there.

OK. I now have a mirror of SLF4J at http://svn-mirror.slf4j.org/repos/.

Yey!

You should be able to update the mirror with the following command in
a post-commit hook:

    svnsync --non-interactive sync http://svn-mirror.slf4j.org/repos/ \
        --sync-username svnsync --sync-password $PASSWORD

(I'll send you the svnsync password in a private message.)

The above svnsync command was added to the appropriate post-commit hook and a similar command to post-revprop-change on svn.slf4j.org.

I noticed that a request made to http://svn-mirror.slf4j.org/repos/ gets redirected to http://svn-mirror.slf4j.org:81/repos/ Is that an issue?

Given that now there is a dependency between svn and svn-mirror via the commit hook, I wonder what will happen if svn-mirror is down or disappears. How reliable would you say that the machine hosting svn-mirror is? (I obviously don't expect 99.99% availability, and just a rough estimate would do.)

The svn-mirror.qos.ch address doesn't seem to resolve for me at the
moment, but I'll set up a similar mirror for that once it does.

There was indeed a DNS problem which has been fixed.

Anyway, I am going to test the svn mirror with a new commit, just after sending this message.

BR,

Jukka Zitting

--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev

Reply via email to