Skip to content

About

WPStation: free, open source WordPress toolkit for ISPConfig 3. Create, detect, clone and stage WordPress sites; safe updates with backup, health check and automatic rollback; one or more nodes. Sandboxed, dry-run by default. Pre-release.

Topics

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

WPStation: the WordPress toolkit for ISPConfig

CI License: BSD-3-Clause ISPConfig 3.3 PHP 8.1+ Status: pre-release

WPStation adds a WordPress menu to ISPConfig 3: create, update, clone and stage WordPress sites across one or more nodes, with a backup, a health check and an automatic rollback around every change. Free and open source, a self-hosted alternative to commercial "WordPress toolkits".

Warning

Pre-release: use at your own risk. WPStation has passed its test plan on test servers, not yet on production. It creates websites, databases and system users and runs commands on your nodes. Try it on a disposable ISPConfig server, keep backups, and read the code first. The authors accept no liability for data loss or downtime (see LICENSE).

The list of WordPress sites in the ISPConfig panel

Why WPStation

  • Updates you can leave running. Every update gets a backup before and a health check after; when the site breaks, it is rolled back on its own and you get an email.
  • Copies in one click. Clone a site to a new domain, on the same node or another one, or give it a staging copy that you push back to production when it is ready.
  • Made for ISPConfig. Websites, databases, users and cron jobs are created through ISPConfig itself, on every node, and your clients and resellers use it on their own sites within their limits.
  • Careful by design. Dry-run by default, never a non-empty folder, everything as the site user, every WP-CLI command in a PHP sandbox, a log of who did what.

WPStation is an independent project: it is not the official "WordPress Manager" extension of ISPConfig. Until November 2026 it was called ispconfig-wp-manager.

Features

Sites

  • New WordPress site: website, database, database user, SFTP or FTP user and WordPress in one form, with per-site PHP version, language, plugins, theme and SSH keys; defaults on a settings page.
  • Existing sites: WordPress installs already on the nodes are found and added to the list.
  • Sites in folders: WordPress in example.com/blog of an existing website, with its own database.
  • Full removal: website, domains, users, cron jobs, databases and the database users nobody else uses, listed before a typed confirmation.

Updates

  • Overview of core, plugin and theme updates of every site, per node and per site.
  • Safe updates with backup, health check and automatic rollback, and a separate button for a new major version of WordPress.
  • Who updates each site: WordPress as before, WPStation for plugins and themes, or WPStation for everything; the automatic updates of WordPress are turned off where WPStation takes over, so nothing is updated twice.
  • Backups and restore from the site page, optionally without wp-content/uploads. They are meant for rollbacks and do not replace the backups of ISPConfig.

Copies

  • Clone to a new domain on the same node or another one, replacing the old address everywhere in the database, serialized data included.
  • Staging, one per site: no mail from PHP, hidden from search engines, updated from production or pushed to production with a list of what will be lost, typed confirmation, backup and automatic rollback.

Tools

  • Maintenance mode that lets logged-in users through, one-click login to wp-admin, password reset of an administrator, debug mode with the log outside the web root, plugins and themes on and off with a health check.
  • Switch between WP-Cron and a real cron job.

Security and operations

  • Known vulnerabilities of WordPress, plugins and themes from Wordfence Intelligence (with your own free API key), with an email and an early automatic update when a fixed version exists.
  • File permission check and fix, hardening switches per site: no file editor, no PHP in uploads, sensitive files and XML-RPC closed, the list of users hidden from visitors.
  • Clients and resellers manage their own sites, within the limits of their ISPConfig package.
  • A log of who asked for what in the panel, with the outcome on the node.
  • Emails through the mail settings of ISPConfig: site ready (never with passwords), rollbacks and failures at once, a daily or weekly summary.

Important

Automatic updates start as soon as dry_run is turned off, for the sites WPStation created. Sites it finds on a node stay with the updates of WordPress until you choose otherwise. To look at a node without any update by WPStation, set updates.auto to n first. See docs/installation.md.

Screenshots

The page of a site
The page of a site: status, backups, updates, tools
Update overview
Updates of every site at a glance
New WordPress site form
A new site from one form
WordPress in a folder
WordPress in a folder of an existing website

Quick start

On a test server with ISPConfig 3.3 and WP-CLI:

git clone https://github.com/stekky81/ispconfig-wpstation /opt/ispconfig-wpstation
sudo /opt/ispconfig-wpstation/install/install.sh --role=master --role=node   # single server

Then add an ISPConfig remote user to /opt/ispconfig-wpstation/config.php and enable the wpstation module for your admin user. Multiserver setups, the remote user's permissions and the step from dry-run to real changes are in docs/installation.md.

Requirements

  • ISPConfig 3.3 (tested on 3.3.2 and 3.3.3), single server or multiserver; see docs/compatibility.md
  • PHP 8.1+ with the sodium and curl extensions on the master and on every web node
  • WP-CLI in /usr/local/bin/wp on every web node, plus sudo, rsync, tar, gzip and a MySQL or MariaDB client
  • A dedicated ISPConfig remote user (System → Remote Users)

How it works

flowchart LR
    subgraph panel["ISPConfig panel (master)"]
        form["Form: New WordPress site"]
        api["Remote API:<br/>website, DB, DB user, SFTP/FTP user"]
        rec["wpstation_site record"]
        form --> api --> rec
    end
    subgraph webnode["Each web node"]
        plugin["wpstation_module and plugin<br/>(server.sh): queue the job"]
        worker["wpstation-worker.php (cron, 1 min):<br/>waits for the vhost,<br/>runs WP-CLI as the site user"]
        plugin --> worker
    end
    rec -- sys_datalog --> plugin
    worker -- status --> rec
Loading

Details in docs/architecture.md.

Documentation

Help test it

Testers wanted, especially on nginx, Debian, MySQL or with a separate database server. A disposable server and an hour are enough: see docs/testers.md.

Automated tests cover the logic that needs no live server, and integration tests run it against real users, MariaDB and WordPress in the CI; the rest follows the manual test plan in docs/testing.md.

composer install
composer test

Security

The design, what a review found and the risks that remain are in docs/security.md. To report a vulnerability, see SECURITY.md.

Important

WP-CLI runs outside the jail of a site, as its own user, limited by a PHP sandbox that is not a jail. If you rely on the jail to contain your clients, read WP-CLI runs outside the jail first.

Contributing

Contributions are welcome: see CONTRIBUTING.md.

License

BSD 3-Clause, the same license as ISPConfig. See LICENSE. ISPConfig and WordPress are trademarks of their respective owners; this project is not affiliated with them.

About

WPStation: free, open source WordPress toolkit for ISPConfig 3. Create, detect, clone and stage WordPress sites; safe updates with backup, health check and automatic rollback; one or more nodes. Sandboxed, dry-run by default. Pre-release.

Topics

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages