Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
App code changes for Galago moving to new domain.
IMPORTANT: Do NOT just merge and deploy. This change must be deployed to Prod at the same time we update the GitHub Pages custom URL for Galago. I believe all the CZI infra stuff is in place for the making the GitHub Pages change, but GitHub Pages change AND the deployed app code must change for the Galago link out to work correctly. If only one of those is done but not the other, the link out will break until the other is completed.
Context:
With the hand-off to Theiagen, we're moving Galago to a new domain. It currently lives at
galago.czgenepi.org
, but since we're basically sunsetting that domain, we need to move it. It will now live as a sub-domain under CZI Science atgalago.cziscience.com
. Since Galago is entirely browser-based, we do not serve it via AWS like most of our other CZI apps. Instead, it lives as a GitHub Page with a custom domain. I've worked with CZI Central to set up the appropriate records so GitHub Pages can use the new domain. However, because GitHub Pages only supports a single custom domain at a time, we have to switch the custom domain setting at the same time we deploy this app code. Nothing breaks permanently if they don't deploy simultaneously, but the Galago link out will be broken until both aspects are complete.Once this PR is merged and deployed to Staging, the Galago link out will be broken there. I'll then coordinate with Central to make sure we're ready to switch over, do a Prod deploy, and change the GitHub Pages custom domain setting at the same time.