-
-
Notifications
You must be signed in to change notification settings - Fork 601
Migration to APIs.guru domain #85
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
Comments
We tried GitHub Pages + CloudFlare combo to serve API on So we decided to try S3 for API hosting and so far it looks good. |
We setup new domain using S3 + CloudFront but we still need to setup custom SSL certificate in order to host it under |
We switched to the new backend so starting from now we have everything nicely hosted on AWS with our own SSL certificate. |
Few PRs is still open but we need to move forward and we will shut down old API on 8th Jul. |
Uh oh!
There was an error while loading. Please reload this page.
TL;DR If you using our API please change
https://apis-guru.github.io/api-models/api/v1/list.json
tohttps://api.apis.guru/v2/list.json
We plan to move APIs.guru out of the proof-of-concept stage. Also, we want to improve our visibility in search engines and GitHub search. This involves some breaking changes to better organize URLs/repos and give them meaningful names (api-models R.I.P. 😢). So if you search for something like "Swagger API catalog" you should get APIs.guru at the first page.
As part of this effort, we are moving all our resources to the
APIs.guru
domain (we will continue using GitHub pages under the hood).Here is our migration plan:
22th Jun29th Jun. If you need more time to do migration, please, comment on this issue;On 22th Jun all links to
apis-guru.github.io
will be automatically redirected toapis.guru
.Here is the table of breaking chages which helps you to easily migrate URLs:
All other URLs from
apis-guru.github.io
will be automatically redirected but we still recommend you to rebase them onapis.guru
The text was updated successfully, but these errors were encountered: