Just wanted to let folks know that RubyForge now supports svn+http for read-only access to the svn repositories. For example:
==================== $ svn checkout http://mongrel.rubyforge.org/svn/trunk/ mongrel A mongrel/test A mongrel/test/test_command.rb A mongrel/test/test_redirect_handler.rb A mongrel/test/test_response.rb A mongrel/test/test_stats.rb [ ... etc ... ] ====================
On Sat, 21 Jul 2007, Tom Copeland wrote: > Just wanted to let folks know that RubyForge now supports svn+http for > read-only access to the svn repositories.
Nice, thanks! I had to "tunnel" through our own server in order to checkout the current rubyforge mocha project at my current contract work. It took me several calls, some month and a half of waiting and a formal request for my client company to open the SVN port and then only to my own machine ... ;-). Life will be easier now. *t
-- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions -----------------------------------------------------------
> On 7/21/07, Tom Copeland <t...@infoether.com> wrote: >> Just wanted to let folks know that RubyForge now supports svn+http >> for >> read-only access to the svn repositories. For example:
> Great news and a good occasion to say thanks to Tom for the great > work :)
Even better would be to give a tangible "thank you" to Tom for doing such a damn fine job of maintaining and improving a critical resource to all of us. He likes dark beer and porter. I was thinking of getting some donations via paypal and sending him a thank you gift he could really appreciate.
If you're interested, let me know and I'll see what we can do.
P.S. I don't drink so suggestions on dark beer / porter that can be ordered and shipped via the interwebs would be appreciated.
On Sun, 2007-07-22 at 10:52 +0900, Ryan Davis wrote: > On Jul 21, 2007, at 11:01 , Robert Dober wrote:
> > On 7/21/07, Tom Copeland <t...@infoether.com> wrote: > >> Just wanted to let folks know that RubyForge now supports svn+http > >> for > >> read-only access to the svn repositories. For example:
> > Great news and a good occasion to say thanks to Tom for the great > > work :)
> Even better would be to give a tangible "thank you" to Tom for doing > such a damn fine job of maintaining and improving a critical resource > to all of us. He likes dark beer and porter. I was thinking of > getting some donations via paypal and sending him a thank you gift he > could really appreciate.
> If you're interested, let me know and I'll see what we can do.
> P.S. I don't drink so suggestions on dark beer / porter that can be > ordered and shipped via the interwebs would be appreciated.
Thanks to all for the kind words! And should I receive beer, I promise not to do any sysadmin work on RubyForge after drinking it :-)
On Sun, 2007-07-22 at 06:10 +0900, Tomas Pospisek's Mailing Lists wrote:
> On Sat, 21 Jul 2007, Tom Copeland wrote:
> > Just wanted to let folks know that RubyForge now supports svn+http for > > read-only access to the svn repositories.
> Nice, thanks! I had to "tunnel" through our own server in order to > checkout the current rubyforge mocha project at my current contract work. > It took me several calls, some month and a half of waiting and a formal > request for my client company to open the SVN port and then only to my own > machine ... ;-). Life will be easier now.
Cool. I hope to get svn+https up and running at some point too. As far as I can tell, it seems like svn+ssh and svn+https are mutually exclusive for the same svn repo - either the filesystem has to handle the permissions or mod_dav_svn has to. I'm working on a automated way for a project admin to elect one or another... we shall see....
>> On 7/21/07, Tom Copeland <t...@infoether.com> wrote: >>> Just wanted to let folks know that RubyForge now supports svn+http for >>> read-only access to the svn repositories. For example:
>> Great news and a good occasion to say thanks to Tom for the great work :)
> Even better would be to give a tangible "thank you" to Tom for doing > such a damn fine job of maintaining and improving a critical resource to > all of us. He likes dark beer and porter. I was thinking of getting some > donations via paypal and sending him a thank you gift he could really > appreciate.
> If you're interested, let me know and I'll see what we can do.
> P.S. I don't drink so suggestions on dark beer / porter that can be > ordered and shipped via the interwebs would be appreciated.
Email me off list for some links to the best beer in the world from right here in Oregon, USA. :) The breweries themselves don't appear to ship, but there are retailers who do.
> On Sun, 2007-07-22 at 06:10 +0900, Tomas Pospisek's Mailing Lists wrote: > > On Sat, 21 Jul 2007, Tom Copeland wrote:
> > > Just wanted to let folks know that RubyForge now supports svn+http for > > > read-only access to the svn repositories.
> > Nice, thanks! I had to "tunnel" through our own server in order to > > checkout the current rubyforge mocha project at my current contract work. > > It took me several calls, some month and a half of waiting and a formal > > request for my client company to open the SVN port and then only to my own > > machine ... ;-). Life will be easier now.
> Cool. I hope to get svn+https up and running at some point too. As far > as I can tell, it seems like svn+ssh and svn+https are mutually > exclusive for the same svn repo - either the filesystem has to handle > the permissions or mod_dav_svn has to. I'm working on a automated way > for a project admin to elect one or another... we shall see....
Try using mod_auth_pam to defer HTTP authentication to PAM; then people don't have to pick and choose.
> Yours,
> Tom
-- Paul Duncan <p...@pablotron.org> pabs in #ruby-lang (OPN IRC) http://www.pablotron.org/ OpenPGP Key ID: 0x82C29562
On Mon, 2007-07-23 at 22:41 +0900, Paul Duncan wrote: > * Tom Copeland (t...@infoether.com) wrote: > > Cool. I hope to get svn+https up and running at some point too. As far > > as I can tell, it seems like svn+ssh and svn+https are mutually > > exclusive for the same svn repo - either the filesystem has to handle > > the permissions or mod_dav_svn has to. I'm working on a automated way > > for a project admin to elect one or another... we shall see....
> Try using mod_auth_pam to defer HTTP authentication to PAM; then people > don't have to pick and choose.
