Closed Bug 1269740 Opened 8 years ago Closed 8 years ago

Move docs to S3 / CloudFront

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

Among other things, this gets us S3 support
OK, I need

docs.taskcluster.net CNAME d2riyrukoaoyvi.cloudfront.net
updated in inventory
Assignee: dustin → arich
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1091780
Whoops, this requires schemas and references to be HTTPS, too (bug 1091780)
Assignee: arich → dustin
We're going to leave bug 1091780 open, and primarily use http://schemas and http://references in production, with cloudfront serving both http and https.  The docs site will rewrite the URLs to https://.. dynamically in the browser.
No longer depends on: 1091780
Commit pushed to master at https://github.com/taskcluster/taskcluster-docs

https://github.com/taskcluster/taskcluster-docs/commit/e8554a6ff9cdd6283b0c3b4595c1b13f8d9001f3
Bug 1269740: Convert http to https URLs

This hacks the local copy of docson, as well as the bits of code parsing
data-doc-ref and data-doc-schema, to always load from https URLs, even
if the given URL is http.  This assumes that
https://schemas.taskcluster.net and https://references.taskcluster.net
are the same as their non-https cousins, and that all ref/schema URLs
are from one of those two sites.
OK, automatic publishing requires PutObjectAcl permissions on the bucket, which requires

  https://github.com/taskcluster/taskcluster-auth/pull/62
But aside from that, docs is now served via https on CloudFront.  So, ALMOST fixed.
https://tools.taskcluster.net/task-graph-inspector/#Zs8lJZ3gTKq3qo_DV8-B-Q/Qld44UnNTmKO9JbGZjrm3Q/0 successfully uploaded the docs from the master branch.

>>drops mic<<
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
Blocks: 1238112
Component: Documentation → Services
You need to log in before you can comment on or make changes to this bug.