In this section

  1. 1Set up a local development environmentChoose one installation route, start Zotonic, create a site, and make your first visible change.
  2. 2Prepare an acceptance or production environmentSeparate environments and record how the site is operated.
  3. 3Deploy and verify a releaseApply a tested revision and check the site from a visitor’s perspective.
  4. 4Configure service startup and restart behaviourRun Zotonic under the installation’s service manager.
  5. 5Find the status site and your site's adminThe status site manages the running Zotonic installation. A site's /admin manages that site's content and enabled modules. They have different scopes and can use different credentials.
  6. 6Run Zotonic as a serviceStart a foreground Zotonic process under the host service manager.
  7. 7Tune server limits from measured loadCheck actual limits and workload before changing operating-system settings.
  8. 8Serve HTTPS on a privileged portTerminate public traffic at a reverse proxy while Zotonic stays unprivileged.
  9. 9Configure hostnames and HTTPSAlign DNS, site selection, and certificate termination.
  10. 10Cache selected public assets with VarnishStart with a narrow VCL 4 policy and preserve authenticated responses.
  11. 11Put Zotonic behind nginxForward HTTP and WebSocket traffic with a narrow trust boundary.
  12. 12Keep development and production settings distinctKeep development and production settings distinct.

Also in: Site administration