Skip to content
How to install

Domains and going live

Every new site answers on its dev domain, such as northwind-bakery.dev.example.com. Going live adds the customer’s domains and makes the first one the site’s address. Visitors keep reaching the site the whole time.

The Go live dialog with a customer domain entered
  • Point each domain at the site’s server: an A record for the bare domain and one for www. With a Cloudflare token, the panel can create them for you.
  • Take a backup if the site already has content. Going live rewrites URLs in the database.
  1. Open the site and choose Go live →.
  2. Under Production domains (first = primary), enter the domains, for example northwindbakery.example www.northwindbakery.example.
  3. Leave Keep the dev hostname as a 301 redirect on, so old links still arrive.
  4. Leave Allow search engines on, unless the site should stay out of search results for now. It unticks Discourage search engines from indexing this site in WordPress.
  5. Optional: switch on Point them at this server through Cloudflare. It appears when the panel has a Cloudflare token.
  6. Choose Go live. The dialog closes, and the job console follows the job.

On the site’s Settings tab, edit Domains (first = primary) and choose Update domains. The steps are the same as going live. A new first domain rewrites the URLs in the database again.

The panel runs one job. It checks each domain’s DNS and warns when a domain does not point at the server yet. It then serves the old and new addresses side by side while Traefik gets a certificate for the new ones. It waits up to 90 seconds for the new address to answer over HTTPS. A slow certificate is a warning, and Traefik keeps trying.

Then the new first domain becomes the site’s address. WordPress’s home and siteurl change, and wp search-replace rewrites the old address in every table. The site’s recipes run again for the new address, so licensed plugins are activated for it. With Allow search engines on, search engines are allowed next. A stopped site is started for this step and stopped again.

If a step fails, the old addresses keep working and the job says what went wrong. Running the change again repairs it.

A PHP site gets no URL rewrite and no change for search engines, and its Go live dialog has no Allow search engines. If the site’s own config names its address, change it there too.

  • At most ten domains per site, and a domain belongs to one site.
  • The panel checks DNS but does not wait for it. A domain that points elsewhere gets no certificate until its record is fixed.
  • The Cloudflare option only reaches zones in the account the token belongs to. Other domains need their records created by hand.
  • Changing the domains later leaves search engines as they are. Only going live allows them, and only with Allow search engines on. Otherwise untick Discourage search engines from indexing this site in WordPress under Settings → Reading.
  • A domain a container app takes a path of cannot be taken off its site, and that site cannot be deleted or moved, until the app’s route is gone.
  • A container app does not go live here. Its hosts are the ones its routes name.