-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move website off of RubyForge #734
Comments
Rubyforge may be old and mostly abandoned, but at least for website hosting it worked well for over 5 years until yesterday. If Rubyforge does go away for good, of course Sequel will migrate to something else, but at this point I'm assuming the problem is temporary and will be fixed. If RubyForge hasn't been fixed by Monday, then we'll migrate to a new webhost. Note that you can access the docs locally on any Sequel checkout, via |
what about utilizing GitHub pages? |
I don't think GitHub pages will work without substantial changes in workflow. I like the current process where where I can just upload a static HTML site via rsync during release. |
@jeremyevans well, RubyForge was hacked and now has been down for days (at least for me)... So I think the advice perhaps was sound ;) And it's kind of necessary now. |
sequel.rubyforge.org is back up now, but it was announced that RubyForge will be closing down in May, so the website will probably be moving within the next few days. |
RubyForge seems old and mostly abandoned. On top of that, this happened:
https://news.ycombinator.com/item?id=6679985
And... RubyForge is down now. Can't access the docs.
I really love Sequel, I'm using it on a major project right now and will be using it in a lot more in the future. It seems like it has enough traction and usage to warrant a website away from RubyForge. I'd be more than willing to help with this.
The text was updated successfully, but these errors were encountered: