WordPress settings
Tune a WordPress site without touching a config file — the fronting web server (nginx or OpenLiteSpeed), PHP limits, OPcache, and page / object caching, applied with one click.
A WordPress site has its own WordPress settings tab — the tunables that usually mean editing
php.ini, an FPM pool, or an nginx config by hand. Here they're a form: change a value, click Save &
apply, and SpipCP relaunches the site so the change actually lands inside the instance.
The fronting web server
You choose how WordPress is served, and you can switch at any time:
| Web server | Caching |
|---|---|
| nginx | A FastCGI page cache served from RAM — the default. |
| OpenLiteSpeed | LSCache (page and object) built in. |
Switching is safe
Changing the web server reinstalls the chosen stack and restarts the origin on Apply. Your content — files and database — is untouched.
PHP limits
The distro defaults are far too tight for modern WordPress and WooCommerce. These are raised to sane values and you can tune them:
| Setting | Default |
|---|---|
| Upload max filesize | 256M |
| Post max size | 256M |
| Memory limit | 512M |
| Max execution time | 300s |
| Max input time | 300s |
| Max input vars | 5000 |
The limits are written as php_admin_value so a plugin can't quietly override them.
OPcache
OPcache keeps compiled PHP in memory — the single biggest WordPress speed win, and the distro gives it far too little:
| Setting | Default |
|---|---|
| Memory | 256 MB |
| Max files | 20000 |
| Validate timestamps | On — code changes take effect immediately. Turn off for maximum production speed. |
Caching
| Cache | What it does |
|---|---|
| Page cache | Serves whole pages from RAM (nginx FastCGI cache; OpenLiteSpeed uses LSCache regardless). |
| Object cache | Caches database queries in Valkey/Redis. Needs a KV service on the instance — when there's none, it's a safe no-op. |
Apply is honest
Save & apply validates your input, persists it, and relaunches the site — the same process the first launch ran, never a faked in-place write. The status goes to launching; watch the Deploys tab for the result. If something is wrong, the site reports it instead of pretending it applied.
→ Launch a WordPress site: Sites. · The web servers on offer: What you can install.
Rust sites
Point SpipCP at a Rust repo and get a single binary, built with cargo and supervised by systemd on its own port — a compile error fails the build, never a broken running site.
Blueprint authoring
How a site type is defined — the blueprint, its required services, environment, install steps, the smoke check, the beta badge, and how to add a new one.