Skip to content
How to install

Create a site

The New site wizard creates a WordPress site in four steps: Name & domain, WordPress, Plugins and Review. A job then builds the site, which answers on its dev domain once the job is done.

Since 0.3.3 Type at the top of the first step picks WordPress, PHP or Container. A PHP site has no WordPress, so the wizard has three steps for it: Name & domain, PHP and Review. A container app runs your own image, with the steps Image, Settings and Routes in between.

The New site wizard's first step with a site title entered
  1. Open Sites and choose New site.
  2. Enter a Site title. Site name (slug) follows the title. The slug names the container, the database and the dev address. It is permanent, so change it now if you want another. On a fleet, pick the Server. Choose Continue.
  3. Fill in Admin username and Admin email. Leave Generate a strong admin password (shown once after creation) on, or turn it off and type a password of at least 10 characters.
  4. Pick the Language and the PHP version. Leave Discourage search engines from indexing this site on while the site is not public yet. Choose Continue.
  5. Tick the Catalog plugins you want. The catalog’s default plugins start ticked, as does one made a default while the wizard is open. Add others under More plugins from wordpress.org, then choose Continue.
  6. Check the Review step and choose Create site. A recipe marked Not set up is skipped, because a value it needs has not been entered yet.

The wizard starts from the defaults under Settings → Sites: Default PHP version, Default language, Default admin email, and Default server on a fleet.

Switch on Use my own domain instead of a dev subdomain and enter the domains under Domains (first = primary). The site is then created live on those domains, with no dev address at all. Point their DNS at the server first. Until then, the site has no certificate.

The wizard starts a site.create job and opens the site’s page, which shows the job’s log until the site is made. The job console follows the job too. In order:

  • It creates the site’s folder, network and database.
  • It starts the container with no route to it, so no visitor can reach the WordPress installer.
  • It installs WordPress with your admin account, sets pretty permalinks, and removes Akismet and Hello Dolly.
  • It installs the language pack and the plugins, then runs their recipes.
  • It makes the site reachable and checks that it answers.

A plugin that fails to install or to activate is a warning, and so is a recipe the vendor refuses. The site is created anyway. When the job is done, the site’s tabs appear. A generated admin password shows above them until you choose Done, only in the browser tab you created the site from.

A new site follows the Page cache default in Settings → Sites, which is on, and its object cache is off. See Caching.

If a step fails, the job removes everything it created, and the slug is free again. The page then shows the error and the log. Back to the form opens the wizard as you filled it in.

  • The slug cannot be changed later. A few names are reserved, such as admin, api, www, new, bulk and import.
  • A site has at most ten domains, and a domain belongs to one site only.
  • Search engines stay discouraged until the site goes live, or until you untick the setting in WordPress. Going live allows them unless you untick Allow search engines there.
  • If the cleanup after a failure fails too, the site stays as Error. Delete site on its Settings tab removes it.
  • The browser keeps what you entered only until the page is reloaded. After a reload, a failed site offers New site, which starts with an empty form.