Publish and preview
Make a page public, share a preview link that works for 15 minutes, change its address with a 30-day redirect, take it offline or delete it.
The nrc monitor status-pages commands need CLI 0.23.0 or later.
Publish
Publishing makes the page public at its address within a minute, along with its
page.json and Atom feed.
nrc monitor status-pages publish acmeThrough the API: POST /status-pages/{id}/publish.
- A page needs at least one component. Otherwise the API answers 409.
- An organization with unpaid invoices can't publish (402). Pages that are already published stay up.
- Publishing a published page changes nothing.
Preview links
A preview link opens the rendered page, published or not, as the public would see it, under a preview notice. It works for 15 minutes.
nrc monitor status-pages preview-link acmeThrough the API: POST /status-pages/{id}/preview-link returns url and
expiresAt.
Anyone with the link can open it until it expires, so share it as you would a draft. Preview pages ask search engines to leave them out and are not cached. A new page may take up to a minute to appear in a preview, because its first snapshot is built after you create it.
For tools, GET /status-pages/{id}/preview returns the same data as JSON: the
page and its history.
Change the address
Change the slug to move the page.
nrc monitor status-pages update acme --slug acme-incOn a published page:
- The new address is live within a minute.
- The old address redirects to the new one for 30 days, keeping the path, so links to an incident keep working.
- The old address is held for those 30 days. No other organization can take it, so an old link never lands on someone else's page.
- If you move the page again, earlier addresses redirect straight to the newest one, each until its own 30 days are up.
- You can move back to an old address while it is yours.
On an unpublished page, a slug change leaves nothing behind.
A slug that is taken or held answers 409 with the reason SLUG_TAKEN.
Unpublish
Unpublishing takes the page offline: its address answers 404, and its custom domain stops serving it. Its layout and posted incidents stay, and preview links keep working. Its old addresses are given up straight away, so another organization can take them.
nrc monitor status-pages unpublish acmeThrough the API: POST /status-pages/{id}/unpublish.
Delete
Deleting removes the page with its layout and posted incidents, takes it offline and gives up its old addresses. The monitors it showed aren't touched.
nrc monitor status-pages delete acmeThrough the API: DELETE /status-pages/{id}.
Post incidents
Tell the public what is happening. Posts are separate from your monitors' incidents, carry a series of updates, and move to the page's history when resolved.
Custom domains
Serve a status page from a subdomain you control, such as status.acme.com. Prove you own it with a TXT record, point a CNAME at Norcube, and the page goes live there with its own certificate.