Closed nickytonline closed 1 month ago
Name | Link |
---|---|
Latest commit | ab6c7749798f375055010afc340937bb90f4930a |
Latest deploy log | https://app.netlify.com/sites/design-insights/deploys/67059015dd4be40008424a20 |
Deploy Preview | https://deploy-preview-4157--design-insights.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | |
Latest deploy log | https://app.netlify.com/sites/oss-insights/deploys/6706bc5efaf98a16b3c376dc |
Deploy Preview | https://deploy-preview-4157--oss-insights.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@BekahHW @isabensusan @open-sauced/engineering, feel free to suggest better wording.
This should be a single page deployable from a
downtime
branch: this way, we can simply flip the deployment ofapp.opensauced.pizza
on Netlify to thedowntime
branch.If that doesn't track with how we'd execute on this, let me know.
Yeah I can do that. It's simpler. Update incoming.
This should be a single page deployable from a
downtime
branch: this way, we can simply flip the deployment ofapp.opensauced.pizza
on Netlify to thedowntime
branch. If that doesn't track with how we'd execute on this, let me know.Yeah I can do that. It's simpler. Update incoming.
One file now, and the updated netlify.toml to handle the redirects during downtime.
https://github.com/open-sauced/app/tree/nickytonline/downtime-page
Great: can we set the target branch to be a new downtime
branch instead of beta
? That way, we can merge to that branch and target it for Netlify deploys if needed!
Description
A temporary downtime page as we do our database migration. It'll get merged to a pretty much empty branch,
downtime
, and we will deploy this branch first to beta to test by pointing the to thedowntime
branch in the Netlify UI, and then prod just before we begin the database migration.Once the database migration is complete in production, we'll change the branch production is pointing to in the Netlify UI, and we'll redeploy or rollback to the previous production release.
Related Tickets & Documents
Relates to #4156.
Mobile & Desktop Screenshots/Recordings
Steps to QA
To test, navigate to any page and it redirects to
/downtime.html
.e.g.
https://deploy-preview-4157--oss-insights.netlify.app/ -> https://deploy-preview-4157--oss-insights.netlify.app/downtime.html
https://deploy-preview-4157--oss-insights.netlify.app/u/nickytonline -> https://deploy-preview-4157--oss-insights.netlify.app/downtime.html
https://deploy-preview-4157--oss-insights.netlify.app/workspaces/a5b9c1f5-8f01-4f61-a6b7-09943ef9e069 -> https://deploy-preview-4157--oss-insights.netlify.app/downtime.html
https://deploy-preview-4157--oss-insights.netlify.app/workspaces/explore -> https://deploy-preview-4157--oss-insights.netlify.app/downtime.html
Tier (staff will fill in)
[optional] What gif best describes this PR or how it makes you feel?