Skip to content
How to install

Site settings

A site’s Settings tab switches its PHP version, changes its domains, sets its caches and its container limits, and deletes the site. Stopping, starting and rebuilding its container are on the Overview tab.

A PHP site’s tab also has Web root, Cron and Run a command, and of the caches only Redis. A container app’s tab has cards of its own: its image, routes, environment, mounts, health check and how it runs.

A site's Settings tab: PHP version, domains and the danger zone

Under PHP version, pick a Version and choose Switch. The job recreates the container with the new PHP image, and files and the database stay as they are. If the site does not answer on the new version, the job puts the old container back and fails.

A version is a PHP branch, such as 8.4. The site runs the release in its server’s image of that branch, such as 8.4.27. Its Overview tab shows the release.

To change the site’s domains, see Domains and going live.

/srv/sites/<slug>/config/uploads.ini holds the PHP settings of the whole site. Edit it on the server, then choose Restart.

A .user.ini changes them for the PHP scripts in its folder and below it. WordPress’s pages all run from the site’s root, so settings for them go in the root .user.ini. PHP reads a change to it within 5 minutes, with no restart.

upload_max_filesize = 128M
max_execution_time = 300

Since 0.3.3 Sites run PHP in PHP-FPM, and Apache no longer knows php_value and php_flag. Such a line in a .htaccess gives a 500 for its folder. Inside <IfModule mod_php.c>, it does nothing.

The panel moves these lines to .user.ini when a site moves to PHP-FPM. It does the same after an import, a refresh, a restore, a move to another server, and an update of WordPress, a plugin or a theme. On a PHP site, it does so after a zip is unpacked on the Files tab. Each line stays in the .htaccess, commented out, after # Moved to .user.ini by WPL7:. php_flag engine off has no such setting, so a deny for PHP files takes its place.

The same pass reads every .user.ini that PHP-FPM has not run with yet: when a site moves to it, after an import or a refresh, and after a restore or a move of files from before the site moved. It comments out what would hurt here: a path from another host, open_basedir, and limits lower than the site’s own. A .user.ini the site has run with on PHP-FPM stays as it is. [PATH=] and [HOST=] sections are commented out in any of them, because PHP-FPM crashes on them. The job log lists every line it changes.

The Overview tab has the buttons:

Button What it does
Stop Stops the container. Visitors get a 404 until it starts again.
Start Starts the container.
Restart Restarts the container.
Recreate container Builds a new container from the site’s current settings: networks, limits, mail login and certificate. Files and the database stay. On a site that could not move to PHP-FPM, it tries the move again.
Clear cache Empties the site’s page cache, and Redis when it runs. See Caching.

A WordPress job on a stopped site, such as an update, starts the site for the job and stops it again afterwards.

Every site container gets the limits under Settings → Sites → Site container limits, unless the site has its own. Saving reaches the existing sites at once, without a restart. Lifting the CPU cap with 0 is the exception: it restarts each site once.

Field Default Note
CPU cores per site 2 Fractions allowed. 0 means uncapped.
Memory per site (MB) 512 The container is killed if it exceeds this.
Processes per site 512 At least 64, because a site runs nginx, Apache and PHP. A lower value saved earlier counts as 64. 0 means uncapped.

PHP and Redis follow the site’s memory and CPU limits:

What How it is worked out At 512 MB and 2 cores
OPcache Three eighths of the memory, from 32 MB to 192 MB 192 MB
PHP workers What the memory leaves after OPcache, one per 32 MB. At least 2, and at most 5 per core 10
Redis, when it is on An eighth of the memory, at least 16 MB 64 MB

One worker stays ready, and more start each second while none is idle. A burst of requests past the workers waits its turn. A site with no CPU cap counts the cores of its server. When a change alters these sizes, PHP-FPM reloads: OPcache starts empty, and requests still running after 10 seconds end.

Since 0.3.3 A site can have more, or less, than the default.

A site's Container limits card with memory set to 1024 MB and the other two fields on the default
  1. On the site’s Settings tab, under Container limits, fill in CPU cores, Memory (MB) or Processes.
  2. Choose Save limits.

An empty field uses the default, which the field names under it. Processes is at least 64 here too. To put a limit back on the default, clear its field and save. The change reaches the container at once, without a restart. Lifting the CPU cap with 0 restarts the site once.

The site keeps its own limits when the defaults change. Settings → Sites lists the sites with limits of their own, under Site container limits.

  1. On the Settings tab, under Danger zone, choose Delete site.
  2. Leave Take a final backup first (kept until you delete it) on to keep one last backup.
  3. Since 0.3.0-beta.2 To remove the site’s other backups too, remote copies included, switch on Delete its existing backups too. It appears when the site has backups. The final backup, if you take one, is kept.
  4. Type the site’s slug and choose Delete site.

The job takes the final backup and releases licensed plugins at their vendors. It then removes the container, the FTP logins, the databases, the files and the site’s network. Backups outlive the site, under Backups → All backups. If a step fails, the site is left as Error, and deleting it again finishes the job.

Limit Value
A request body 1 GB, or post_max_size in uploads.ini plus 16 MB when that is more. Past it, a 413
Bodies of 1 MB or more at once, per site 16. The next one gets a 429
One request header line 8 KB
All request headers About 60 KB
One response header line 8 KB. Past it, a 500
All response headers 32 KB. Past it, a 502
One PHP request About an hour, at most 80 minutes
Running requests at a stop 5 seconds. Recreate container ends them at once
  • php_value and php_flag in a .htaccess give a 500 for its folder, and do nothing inside <IfModule mod_php.c>. Use .user.ini.
  • A change to a .user.ini takes up to 5 minutes.
  • A higher upload limit set only in .user.ini gets a 413 past the body limit above. LimitRequestBody in a .htaccess has no effect on PHP files.
  • PHP runs only in files named .php. A file a .htaccess hands to PHP under another name answers 403. One handed to a handler Apache does not have, such as cPanel’s ea-php, is sent as it is, source included. The job log names each such line. Rename the file to .php.
  • A download PHP serves holds a worker for as long as it runs.
  • A PHP page with Last-Modified or ETag can get a 304 or 412 from the server, even if its body changed.
  • A plain script that does not load WordPress gets a 500 for a header line with no colon, and http_response_code() does not replace a status it set with header(). A plugin that registers its own header_register_callback brings both back on WordPress’s pages.
  • apache_get_modules, apache_get_version, apache_getenv, apache_setenv, apache_note, apache_lookup_uri, apache_response_headers and virtual do not exist under PHP-FPM.
  • SetEnv no-gzip does not stop Brotli. <IfModule mod_headers.c> blocks now apply, and Header unset needs always.
  • Repeated response headers are merged into one, except Set-Cookie.
  • A URL with %00 in it gets a 400.
  • A site gets at most the CPU cores its server has. A higher CPU limit gives it all of them.
  • Switching PHP replaces the container, so the site does not answer for a few seconds.
  • If a recreated container starts but does not answer, Recreate container leaves it in place. The job log warns about it. A container app’s goes back to the old one instead, as a deploy does.
  • A vendor that cannot be reached keeps its license activation. The job warns, and the site is deleted anyway.