Skip to content
How to install

Settings

Since 0.3.0-beta.2 Settings holds what applies to the whole panel, in seven tabs. The first five are one form. Save settings saves the changes on every tab at once, and a dot marks a tab with changes not saved yet. DNS and Updates act at once, with buttons of their own.

On the stable channel, the same settings are cards on one long page, without the DNS tab.

Settings → Sites with the site defaults and the container limits

Site defaults prefill the New site wizard: PHP version, language, admin email and, with several servers, the server. An API request that leaves out the admin email uses this one too.

Since 0.3.3 Page cache and Keep pages for, in the same card, apply to every site that follows them. A save reaches those sites at once, and empties their page caches. Page cache is on by default, and Keep pages for is 10 hours, which is also the most. A site can say otherwise in its Caching card. See Caching.

Site container limits cap each site’s CPU, memory and processes. Saved changes reach every site at once, without a restart, except lifting the CPU cap, which restarts each site once. A site can set its own on its Settings tab. See Site settings.

Limit Default
CPU cores per site 2
Memory per site (MB) 512
Processes per site 512

Processes per site is at least 64, because a site runs nginx, Apache and PHP. 0 means uncapped.

FTP & SFTP allows or stops FTP and SFTP logins on every server, and sets their ports. See FTP and SFTP logins.

Schedule (cron) sets when the scheduled backups run, 03:00 by default. Keep last N scheduled backups per site sets how many stay, 10 by default. The card lists each server’s backup location, which Backup storage changes.

Since 0.3.0-beta.3 Delete site backups after (days) and Delete panel backups after (days) have the nightly housekeeping delete older backups. Both are 0 by default, which deletes nothing. A site can set its own on its Backups tab, and the card lists the sites that do. Delete old backups says which backups this takes.

Since 0.3.0-beta.3 Back up before updates decides whether an update backs a site up first: Always, Ask each time or Never. It is Ask each time by default. A site can set its own on its Backups tab, and the card lists the sites that do. See Choose whether updates back up first.

WordPress updates & security sets how often every site’s plugins, themes and WordPress are read again, and whether they are rated against known vulnerabilities. See Updates and known vulnerabilities.

Malware scans and Trusted proxies are described in Malware scans and Site protection. Adminer turns the Adminer buttons on a site’s Database tab on or off: see Adminer. The fleet’s default protection is under Sites → Security, and blocking under Servers → Security.

Setting Default
Keep traffic history for (days) 30
Flag a site above (messages / hour) 200
Suspend a site above (messages / hour) 1,000

The mail relay itself is set in deploy/.env, as How mail works explains.

Since 0.3.0-beta.2 This tab holds the Cloudflare token and each server’s wildcard certificate, as Cloudflare DNS describes.

Setting Default
Uptime check (seconds) 60
Container stats (seconds) 60
Disk scan (minutes) 30
Keep visitor statistics for (days) 90
Keep visitor addresses for (days) 7

New intervals apply after a panel restart. Turning off Record visitor addresses deletes the addresses already stored. See Visitor statistics.

Since 0.3.0-beta.3 Send alerts to is where the panel emails you. Empty, alerts only go to the panel’s log. Suspended mail, malware findings, failed offsite copies, a server low on disk and new releases are always sent there, and so is a new image waiting for a container app that asks first. Since 0.4.1 So are PHP security releases: php.net’s notice of one, its release, and how its sites moved. A server is low on disk with less than 10% of it free, and fine again at 15%. Five switches, all on by default, add these:

Switch Emails when
Site down, and back up A site misses three uptime checks in a row, and again when it answers
New vulnerabilities A scan finds a known vulnerability not emailed before
Failed backups A backup fails, at most once a day per site
External sites: WPL7 Connect not answering, certificate expiring The plugin of a site hosted elsewhere misses three hourly checks, and a week before that site’s certificate expires
Container apps: a deploy that failed A container app’s new image does not go in, once per image

Each alert is sent once, and kept track of across restarts. One the mail relay does not take is tried again at the next check, ten minutes later at the earliest. A site that is back up, or a certificate that was renewed, ends it, and the email for that still says how long the trouble lasted.

This tab shows the installed version, its channel and the last check, with Check now and the button that applies a new version. See Updating WPL7.

Look up domain expiry dates in Monitoring controls the registry requests used by Reminders. Switching it off keeps saved dates and stops domain requests.

  • Settings apply to the whole panel. A site’s own PHP version and protection are on its own page.
  • Every admin can change every setting.
  • The panel’s domain, the mail relay and other values in deploy/.env are not here. See Configuration.
  • The backup schedule and other values read from deploy/.env on the first boot belong to the panel afterwards. Editing the file changes nothing.