Skip to content

Commit

Permalink
Merge pull request #1903 from metacpan/mickey/update_old_api_links
Browse files Browse the repository at this point in the history
update links to new API in docs
  • Loading branch information
oalders committed Jun 4, 2017
2 parents c8f19a3 + 771f4bc commit 93aecb9
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions News.md
Expand Up @@ -3,10 +3,10 @@ Title: SSL improvements
Date: 2014-12-02T19:30:00

Our servers have had their SSL configuration upgraded,
so we now get an A rating on [SSL Labs](https://www.ssllabs.com/ssltest/analyze.html?d=api.metacpan.org).
so we now get an A rating on [SSL Labs](https://www.ssllabs.com/ssltest/analyze.html?d=fastapi.metacpan.org).

[Fastly](https://www.fastly.com) who serve all our content
other than the [api](https://api.metacpan.org/) already had
other than the [api](https://fastapi.metacpan.org/) already had
tight configs... and now so do we. I'd like to thank then for providing
both examples, support and an IRC channel where Donald Stufft
from the Python infrastructure team was able to help out.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -23,7 +23,7 @@ commands can be converted to:

## Local configuration changes

The backend defaults to `api.metacpan.org`. Running a local API server is
The backend defaults to `fastapi.metacpan.org`. Running a local API server is
optional and not required to hack on the front-end. The address to the API
user can be changed in the `metacpan_web.conf` file. Ideally you would create a
new file called `metacpan_web_local.conf` that contains
Expand Down

0 comments on commit 93aecb9

Please sign in to comment.