Build and deploy dev website via CI
(FOLIO-832)
|
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Documentation |
| Affects versions: | None |
| Fix versions: | None | Parent: | Build and deploy dev website via CI |
| Type: | Sub-task | Priority: | P3 |
| Reporter: | Peter Murray | Assignee: | Michael Winkler |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3 hours | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
The FOLIO developer site is transitioning to being hosted by AWS in a CloudFront-proxied S3 bucket. The AWS stack will also allow for sub-sites to be created based on pull requests to the GitHub repo. In order to facilitate this, we need to delegate DNS for 'dev.folio.org' to AWS. These DNS entries are needed:
Route53 on AWS Is already set up to respond to A requests for `dev.folio.org` to the existing GitHub Pages site, so users will not see a change. |
| Comments |
| Comment by Peter Murray [ 21/Nov/17 ] |
|
Request sent to Rachel. |
| Comment by Peter Murray [ 05/Feb/18 ] |
|
Michael Winkler: We're on the home stretch for making this change. Can you replace the DNS entry for `dev.folio.org` with a delegation to these nameservers?
The content on AWS is in sync with what is hosted on folio-org.github.io, so users will not notice a difference. Well, one difference: they will be automatically redirected to HTTPS by AWS CloudFront. |
| Comment by Peter Murray [ 08/Feb/18 ] |
|
Worked with Michael Winkler to make the cutover. After fixing a CloudFront configuration problem (set the alternate CNAME to `dev.folio.org`!) the AWS-based developer documentation site is running. Waiting for AWS to fully populate the alternate CNAME change throughout the CloudFront network before officially calling this done. |
| Comment by Peter Murray [ 09/Feb/18 ] |
|
Now done. |