sunset badgr.co

[chadwhitacre]

There can't be that many people using Badgr.co yet but I know there's a few. I'm going to start tweeting and linking here to hopefully let people know that Badgr.co is going away. I suppose we could leave some overlap with Shields.io once that's launched. Probably for how much traffic Badgr.co is getting a month of overlap would be fine (it's double the SSL cost $20/mo).

[chadwhitacre]

First notice: https://twitter.com/whit537/status/379632872799219712.

[chadwhitacre]

It'd probably be good to RT or post from Shields_io Twitter since that started life as Badgr_co.

[olivierlacan]

And you shall be retwote.

[chadwhitacre]

:-)

[balupton]

Can we get a migration guide? Right now I have:

[![Gittip donate button](http://badgr.co/gittip/docpad.png)](https://www.gittip.com/docpad/ "Donate weekly to this project using Gittip")

What would be the sheilds.io equivalent? It seems from the readme, that shields.io is more of a standard for how the buttons should look, rather than a service providing buttons.

[chadwhitacre]

@balupton Thanks for joining us here. We need to update the README. Shields started out as a standard and is evolving into a service (see #15 for details). I'll follow up here when we have steps to migrate.

[colindean]

It'd be nice if we could scan github for READMEs and whatnot that may contain badgr.co references, file issues with some kind of template ("The file $filename contains a reference to badgr.co. It is be replaced with shields.io. Pleasee there for more information"), or perhaps even submit a pull request automatically with the references changed.

Github search won't seem to show me anything useful, not even showing the ~half dozen projects of my own that have badgr.co image references in them. Google search not as effective as I'd like, either.

[chadwhitacre]

I don't think there are that many out there to justify too much work. I was thinking we could check Referer in our server logs.

[colindean]

That would probably be almost as good, provided that people are actually loading the images ;-)

[olivierlacan]

I'm pretty sure GitHub caches all external assets to prevent mixed content issues with SSL.

On Mon, Sep 16, 2013 at 8:17 PM, Colin Dean notifications@github.com
wrote:

That would probably be almost as good, provided that people are actually loading the images ;-)

Reply to this email directly or view it on GitHub:
#63 (comment)

[chadwhitacre]

cc: @twolfson

https://twitter.com/twolfsn/status/382049092580298752

[chadwhitacre]

@olivierlacan Are we ready for another announcement on the Shields_io Twitter account?

All: New URL base is http://img.shields.io/. If you need SSL then watch #66.

[balupton]

Sweet! Added support to bevry/projectz

[olivierlacan]

@whit537 Sure, what do you want to announce?

[chadwhitacre]

@olivierlacan That shields.io is live and people should switch to img.shields.io. No?

[chadwhitacre]

s/live/soft-launched

[chadwhitacre]

:)

[nathany]

Perhaps http://badgr.co/ should redirect to http://shields.io/?

Do we want to attempt maintain API compatibility through redirects from one or more past services?

[chadwhitacre]

http://badgr.co/ now redirects to http://shields.io/ (using a meta tag).

[chadwhitacre]

Reopening while I actually work on this. :-)

[chadwhitacre]

Here's where the refresh happened: badges/badgr.co@56a6ac4.

[chadwhitacre]

I've turned off SSL on Badgr.co. The app is now running without additional cost to us at Heroku and I suppose we can let it run for "ever." Non-SSL images will work until they don't.

[chadwhitacre]

Posted an announcement on Twitter.

[chadwhitacre]

Considering this done. At some point in the future we can prune the Badgr.co app entirely.

[chadwhitacre]

Wait, where did it go? http://badgr.co/ is timing out for me now. :-/

[chadwhitacre]

Ah! It's because I removed the SSL endpoint, and that's what we're CNAMEd to. Fixing ...

[chadwhitacre]

Okay! Fixed. :-)