Preview, restore, and reset

This is the page for "reset to default" and for getting a real client's content onto your test site.

Two very different places

PlaceWhat it isWho sees it
Your previewA private test copy of the product on your workerOnly people with your preview address
A deployed siteA real client site on Staging, POC, or productionReal visitors, if the site is live

Almost all work happens on your preview. The agent only touches a deployed site when you name it and ask for content work there.

Your preview

Every worker has its own preview. The address follows your name:

  • Website: https://<your-name>.agent.gopublic.dk
  • Admin: https://admin.<your-name>.agent.gopublic.dk

Out of the box it runs the template: an empty-ish demo client, not a real customer. That is the safe place for design work, new modules, and most bug fixes.

Anything you upload there (pictures, files) stays on your worker. It never reaches the real CDN.

"Reset to default"

Reset to default wipes your preview back to the template. Nobody else's preview is affected.

Say any of:

  • Reset to default
  • Reset the preview
  • Go back to the template
  • Clear the restored client

The agent then puts the empty template database back, clears the cache, restores the template themes, restarts the preview, and checks that the site answers before it reports back.

What you lose

  • Pages, modules, users, and other content created on the preview
  • A restored real client (Trafikstyrelsen, stps, …)
  • Demo data the agent set up for you
  • The Agent wiki pages on your preview (ask "show me the agent wiki" to get them back)

What you do not lose

  • Pull requests and branches already on GitHub
  • Any real site — Staging, POC, production
  • Unpublished code edits on the worker. Reset is about content and data. If you also want the code thrown away, say it in those words: "Discard the local code changes."

Restore: put a real client into your preview

Use this when you need that customer's pages and data: a content setup that only exists there, or a bug that only shows with their structure.

Say it clearly, with the client and the environment:

Restore stps from production into this worker.

Pull the silver client Trafikstyrelsen into the agent.

Load danieltest from POC.

The agent copies the client into your isolated preview. The real customer site is never touched.

What restore mode protects

  • You can click around, log in, search, try forms — on the preview.
  • Pictures are read from the real CDN, so they look real. They are not a second copy you can edit.
  • The agent cannot write to the customer's real media library, and cannot fire newsletters, imports, or background jobs from the restored copy.

This is not a restore request

None of these copy a client. The agent stays on whatever is already on the preview and asks if unsure.

  • Fix the freeze on https://admin.intranet.trafikstyrelsen.dk/…
  • The news module is wrong on client X
  • Can you open the exact production page?

A bug on a client site is reproduced on the template first. Restoring the client is the heavy last resort, and the agent asks before doing it.

Reset vs restore — one sentence each

You wantSay
The empty demo againReset to default
Customer X's data on your previewRestore X from production / silver / gold / POC
A change on the real Staging or POC siteName the site and say what to change (see Everyday tasks)
A product bug fixedDescribe the bug. Do not restore unless you truly need their data.

After a reset or restore

The agent prints a status block: which client is active, and which branches the product repos are on. Read it. If it looks wrong, say so before you continue.