search

bower / registry

The Bower registry
https://registry.bower.io/packages
MIT License
292 stars 66 forks source link

bower.heroku.com legacy routing #89

Closed desandro closed 9 years ago

desandro commented 10 years ago

Just want to make sure we've resolved Heroku's heroku.com legacy routing. A quick scan of the source doesn't pull up anything. We good?

Hi there,

This is a reminder that Heroku is turning off the legacy “.heroku.com” routing path on September 22nd 2014. This is part of an effort to to standardize on a single, fast, highly available and scalable routing stack for all customers.

You are receiving this email because one or more of your apps is still using the legacy routing and you must take action to ensure continued operation of those apps after the September 22nd deadline.

The following domains which are still receiving legacy traffic are:

bower.heroku.com

Also, you may use the Legacy Routing Analyzer to see which of your apps are affected. Login to your Heroku account and click here.

We recommend that you migrate those affected apps away from the legacy routing infrastructure as soon as possible.

For instructions on how to make the move, please visit this Heroku Dev Center article.

We know that changing DNS settings for live apps requires care and planning, and we will assist with guidance and advice for you to make the necessary updates. If you have any questions about this topic, feel free to open a support ticket.

We will continue to send reminders in the coming months to owners and collaborators on apps that continue to use the legacy routing infrastructure.

Cheers, Heroku team

rayshan commented 10 years ago

Thanks David. I also looked here: https://github.com/search?utf8=%E2%9C%93&q=%22bower.heroku.com%22&type=Code&ref=searchresults

Doesn't look like there's anything current that's at risk.

The only thing I can think of is bower uses bower-registry-client, which may have used the old routing at some point. This can be fixed with people just updating bower to latest version.

Going forward we should use api.bower.io so we have full control over routing. I'll get this up after we get a SSL cert.

rayshan commented 9 years ago

Legacy routing EOL happened on 10-20-2014: https://devcenter.heroku.com/changelog-items/463

Legacy routing analyer shows no recent legacy traffic received: https://legacy-routing.herokuapp.com

Closing.