Skip to content

Day‑2 operations (running your site)

This page is for site administrators doing routine operational tasks.

It’s intentionally lightweight and focuses on what you can do from the Hub and APIs.

Check site status

Open the site's Operations section in the Hub. For an enabled site, it shows live health for the site, NGINX, and storage, plus site conditions. Health refreshes automatically every 15 seconds. Archived sites do not show health data.

The Site Status card shows one of these states:

  • Running: all the containers of the site are ready.
  • Starting: the containers start, or wait to become ready. This is normal after a restart.
  • Not running: at least one container has a problem. The card names the container, the problem, and what to do. Select Load logs to read the logs of that container, or Restart now to restart the site.
  • Archived: the site is archived.

The card also shows the time of the last status change, in UTC.

The Overview also shows whether the site is active or archived, its current storage use, and its retention date.

Set SITE_TOKEN to a Site API token, then call the health endpoint:

curl -H "Authorization: Bearer ${SITE_TOKEN}" \
  "https://<domain>/<space>/<site>/s/api/v2/health/"

Like the rest of the Site API, this endpoint also answers a browser request from a site administrator session, but scripts need the token header above.

Restart a site

Sometimes you need a restart to apply certain changes or recover from a transient issue.

Use Actions → Restart Site in the Hub, or call the Hub API. You must be a site administrator.

Set HUB_TOKEN to an OpenID Connect (OIDC) access token for the Hub API:

curl -H "Authorization: Bearer ${HUB_TOKEN}" \
  -X POST \
  "https://<domain>/hub/api/v2/sites/<space>/<site>/restart/"

Upgrade a site

Use Actions → Upgrade Site in the Hub, or call the Hub API endpoint to rebuild the site with the latest component versions available. The action is shown when an upgrade is available.

curl -H "Authorization: Bearer ${HUB_TOKEN}" \
  -X POST \
  "https://<domain>/hub/api/v2/sites/<space>/<site>/upgrade/"

The site is unavailable for a short time while its components restart.

Disable (archive) a site

Use Actions → Archive Site to disable the site. Use Actions → Enable Site to enable an archived site again. These actions are available to site administrators.

Archiving is useful when:

  • the project is finished
  • you want to freeze content
  • you want to stop running components temporarily

A disabled/archived site may still have content preserved, but some actions are blocked (for example: generating new tokens/URLs).

The Actions menu also has Delete Site. This removes the site from the Hub. Confirm your service's data-retention requirements before deleting a site.

View logs

In the site's Operations section, select a container, set the number of lines, and select Load Logs. In high-availability mode, the Hub shows logs for each instance. Site administrators can also use the Hub API.

Use logs when:

  • uploads fail
  • you see unexplained errors
  • health checks fail

If you can’t access logs, your account may not have the right role.

Traffic analytics

On deployments with the analytics integration enabled, site administrators see an extra Analytics section on the site's page. It shows web traffic reports for the site, per week and per month:

  1. Open the site's Analytics section in the Hub.
  2. Pick a recent week or month in the period selectors.
  3. Select Week Report or Month Report.

The first request for a period kicks off report generation in the background, and the Hub asks you to check again in a few minutes. Later requests show the finished report. Archived sites don't offer reports; the section says analytics isn't available.

You can load reports through the Hub API too, as a site administrator:

curl -H "Authorization: Bearer ${HUB_TOKEN}" \
  "https://<domain>/hub/api/v2/sites/<space>/<site>/analytics/weekly/"

Without parameters this returns the most recent complete week. Pass ?reference_date=YYYY-MM-DD for the week containing that date, or an explicit ?start_date=YYYY-MM-DD&end_date=YYYY-MM-DD range. Replace weekly with monthly for monthly reports.

Read-only mode

The platform can be put into a global read‑only mode (usually during maintenance).

In read-only mode, the Hub blocks write operations. Whether writes to site content are also blocked depends on the platform routing mode. Read operations should still work.

If you can’t edit a site and you’re sure you’re an admin, check whether the system is in read‑only mode.