# Hoe and rubyforge and all that **URL:** \ **Category:** Ruby\ **Created:** [October 17, 2006, 5:21am UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419 "2006-10-17T05:21:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tbcox23](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/b9bd4f/32.png) [@tbcox23](https://www.ruby-forum.com/u/tbcox23)\ **Post date:** [October 17, 2006, 5:21am UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419/1 "2006-10-17T05:21:00Z")
Hi all - We’ve started using HTTPS to make RubyForge logins more secure. However, this will probably hose up the various utilities that folks are using to automate releases - like hoe, and I think Ara’s got one, and there may be others. Should we turn off HTTPS for a few days to let those utilities catch up? Or just leave it on? Comments/questions welcome, Thanks, Tom ---
**Author:** ![tbcox23](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/b9bd4f/32.png) [@tbcox23](https://www.ruby-forum.com/u/tbcox23)\ **Post date:** [October 17, 2006, 5:25am UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419/2 "2006-10-17T05:25:00Z")
On 06-10-16, at 23:20, Tom C. wrote: > Hi all - > > We’ve started using HTTPS to make RubyForge logins more secure. > However, this will probably hose up the various utilities that > folks are > using to automate releases - like hoe, and I think Ara’s got one, and > there may be others. Should we turn off HTTPS for a few days to let > those utilities catch up? Or just leave it on? Offer both for a period of time until any reasonable project has had time to update and push out a new release. ---
**Author:** ![tbcox23](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/b9bd4f/32.png) [@tbcox23](https://www.ruby-forum.com/u/tbcox23)\ **Post date:** [October 17, 2006, 5:35am UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419/3 "2006-10-17T05:35:00Z")
On Tue, 2006-10-17 at 12:23 +0900, Jeremy T. wrote: > Offer both for a period of time until any reasonable project has had > time to update and push out a new release. Ah, right you are, and it only required some minor code changes. OK, now there’s a Log In/HTTPS link up top there. I’ll remove the code next Monday, say. Thanks for the suggestion! Yours, Tom ---
**Author:** ![tbcox23](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/b9bd4f/32.png) [@tbcox23](https://www.ruby-forum.com/u/tbcox23)\ **Post date:** [October 17, 2006, 9:24am UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419/4 "2006-10-17T09:24:15Z")
Tom C. wrote: > Hi all - > > We’ve started using HTTPS to make RubyForge logins more secure. > However, this will probably hose up the various utilities that folks are > using to automate releases - like hoe, and I think Ara’s got one, and > there may be others. Should we turn off HTTPS for a few days to let > those utilities catch up? Or just leave it on? > > Comments/questions welcome, Is this why my SVN updates/commits to RubyForge have failed the last few days? Do I need to specify a new URL for the projects? Nic ---
**Author:** ![tbcox23](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/b9bd4f/32.png) [@tbcox23](https://www.ruby-forum.com/u/tbcox23)\ **Post date:** [October 17, 2006, 2:52pm UTC](https://www.ruby-forum.com/t/hoe-and-rubyforge-and-all-that/72419/5 "2006-10-17T14:52:57Z")
On Tue, 2006-10-17 at 16:24 +0900, Dr Nic wrote: > Is this why my SVN updates/commits to RubyForge have failed the last few > days? Do I need to specify a new URL for the projects? Hi Nic - Hm, no, we just added mod\_ssl today, and that shouldn’t affect svn commits. Hm… contact me offlist (removed\_email\_address@domain.invalid) and maybe we can sort out what the problem might be… Yours, Tom