Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Go-live checklist for a customer site

The checklist a host works through before a customer's Exponential site goes public: administrator password and accounts, settings, caches, HTTPS and headers, cron, mail, search, backups with a restore test, monitoring…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/hosting/checklists/new-customer-site-go-live.md

On this page

Go-live checklist for a customer site

This checklist is for the host's system administrator and the customer's site owner, together, in the days before a site goes public on your platform. It assumes the server passed the New server checklist.

Warning

.htaccess slows down every request. When .htaccess files are enabled (AllowOverride anything but None), let alone used, Apache looks for them and reads and evaluates them on every request, in every directory of the path, and page loading times go up drastically (measured). The only real fix is to switch the feature off for the virtual host: AllowOverride None in the HTTPS virtual host, and the rules in the virtual host's own configuration as mod_rewrite rules. That is far faster in production speed tests and well worth the time it takes to optimize a production configuration. Switch over right away: copy the rules of the example HTTPS virtual host into your virtual host (with the static cache, also staticcache_offload.conf), set AllowOverride None, run apachectl configtest, reload Apache and test the site. The same rules for other servers: nginx, LiteSpeed, Caddy, IIS, Velocity (built in); where virtual host rules go in a control panel: Plesk, cPanel, DirectAdmin, ISPConfig. On LiteSpeed or OpenLiteSpeed, the server's own page cache can also answer anonymous visitors and crawlers without PHP: Page caching with LiteSpeed and OpenLiteSpeed.

Site: <domain>        Customer: <customer>        Go-live: <date>        Checked by: <names>

Accounts and passwords

  • To do: The administrator password set at installation is not a default one and is known only to the people who need it (The default administrator password, Change the admin password).
  • To do: Test accounts created during development are removed or disabled.
  • To do: Each editor has a personal account; nobody shares the administrator account.
  • To do: Two-factor sign-in decided for administrators (Two-factor sign-in).

Settings

  • To do: Debug output is off for the public siteaccesses ([DebugSettings] DebugOutput=disabled in the site's settings).
  • To do: The site addresses and siteaccess matching name the production domains.
  • To do: Mail transport and sender are the production ones (Mail delivery).
  • To do: The installation name shown in pages is the production one, where used.
  • To do: settings/override is readable only by the site's system user and its engine or PHP-FPM pool.

Caches and performance

  • To do: The view cache and template cache are on for the public siteaccesses (Caching layers).
  • To do: With Velocity: the response cache is on and cleared after the last deploy (php bin/php/console exp:velocity cache clear --apply --allow-root-user).
  • To do: The front page and the main section pages answer from a warm cache within your plan's target; measured with the benchmark command (Benchmarking a hosted site).

HTTPS and headers

Cron, search, mail

  • To do: The site's crontab runs runcronjobs.php with its parts (Cron jobs); the cronjob console shows the last runs (Cronjob console).
  • To do: The search index is complete (php bin/php/updatesearchindex.php has run after the last import) (Search backends).
  • To do: A test mail from the site (for example a password reset for a test account) arrives and is not marked as spam.

Backups and restore

  • To do: The backup job for this site runs: database plus var/storage, settings/override, settings/siteaccess (What to back up).
  • To do: One backup of this site has been restored on another machine and the restored site opens (Restore and restore tests).

Monitoring and logs

DNS and cut-over

  • To do: DNS time-to-live lowered in advance; the new records ready.
  • To do: The site tested on the production machine through a hosts-file entry before DNS changes.
  • To do: Rollback agreed: how, until when (Migrating customers to your hosting).

Handover

  • To do: The customer knows how to report a problem and what to include (page, time, error reference) (Support tiers).
  • To do: The customer's editors know where the help is: the help dashboard of their administration.
  • To do: The SLA and the backup retention are confirmed in writing.
  • To do: The site's record is complete: versions, database engine, engine, extensions, contacts.

Demo mode.

  • To do: Demo mode off: EXP_DEMO_MODE is set for none of the site's processes (pool, virtual host, .htaccess, unit, crontab); no Demo mode banner in the administration; no demo/mode line in var/log/security.log (Demo mode for hosts).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x