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
Site is down #8
Comments
It had so few visitors per month, so I decided to take it offline, sorry for the bad news! If you care about it and want to host it yourself, I'll be happy to point the domain to you right now and transfer the ownership also. |
:-( |
:-( too |
: ( |
Do you know how much traffic/storage it consumed over a fixed period of time? |
Unfortunately I have not kept any log files. Storage wise I remember MongoDB taking up a couple of hundret MB of disk space. But the real data must be far less than that, no idea why MongoDB took so much space. The traffic was just a few visitors per month, plus some visits from Google bots etc. Sorry that I don't have any real data and just some vague info from what I can remember. |
:(( sad too |
FYI, I'm working to revive this project and have it hosted by the MetaCPAN team. The new location is at https://github.com/CPAN-API/github-meets-cpan. @plu++ for doing such great work on this. :) |
\o/ @oalders++ |
We're getting close to launching this. We'll be hosting it under metapcan.org, but we need another hostname for it. Thoughts? hackers.metacpan.org? |
cc @ranguard ^^ |
|
Best keep it genderless. |
github.meet.metacpan.org |
We are going for gh.metacapn.org - it's 95% configured (metacpan/metacpan-puppet#79 carton/starman etc installed, mongodb installed, nginx configured. DNS and Fastly CDN also done) @oalders just needs to get github credentials deployed and a few other tweaks. |
http://gh.metacpan.org/ is now live and on an hourly cron to upgrade |
👍 Thank you all for doing this. |
I should mention it's also many times faster ( thanks to Fastly CDN ) |
Oh well, in that case: :+2: |
👏 |
The site is unreachable.
Cc: @neilbowers
The text was updated successfully, but these errors were encountered: