WordPress

Last updated

WordPress is the first-class app in Jabali’s Applications Framework.

Tenant workflow? See WordPress (User). Applications framework + other apps? See Applications. This page covers the WordPress-specific install pipeline.

One-click install

/jabali-panel/applications → pick the domain → WordPress → Install.

The wizard collects:

  • Site title, admin username, admin password (or generate one), admin email.
  • Install path (root or subdir).
  • Locale (en_US, he_IL, ar_SA, etc.).

The agent then:

  1. Provisions a MariaDB database + DB user.
  2. Downloads the latest WP via wp core download.
  3. Writes wp-config.php with the DB creds + secret salts.
  4. Runs wp core install (idempotent).
  5. Writes a single-use SSO drop-in (60 s TTL) inside the install dir.
  6. Records the install in application_installs with app_id=wordpress.

Total time: ~25 seconds for a fresh install on a standard VPS.

One-click admin

In the Applications list, each install has an Open Admin button. Clicking it:

  1. The panel writes <install-dir>/jabali-sso-<43-char-nonce>.php.
  2. Redirects the browser to https://<domain>/jabali-sso-<nonce>.php.
  3. The file calls wp_signon() for the admin user, sets the auth cookie, redirects to /wp-admin/, then flocks + unlinks itself.
  4. The systemd reaper sweeps any orphaned SSO files every 30 s (60 s TTL ceiling).

This is the self-deleting SSO file pattern (Installatron / Softaculous style). The earlier magic-link mu-plugin + HMAC callback approach failed and is not in use.

Clone

Applications → Clone → pick source install + destination domain. The agent rsyncs the install dir, dumps + restores the DB into a new DB row, runs wp search-replace on the site URL, writes a fresh SSO file.

Delete

Applications → Delete. Removes the install dir, drops the DB + DB user, removes the install record. Asks twice; destructive.

Auto-updates

Per-install toggle. When on, the panel runs wp core update && wp plugin update --all && wp theme update --all weekly via a systemd-user timer owned by the WP install’s Linux user.

Caching (shipped)

  • Per-domain nginx FastCGI page cache — per-install toggle. Cookie/auth-aware bypass (never caches authenticated requests), per-domain TTL, Vary-aware, revalidates expired entries, and targeted + full purge.
  • Jabali Cache plugin (jabali-cache) — ships WordPress object-cache + page-cache drop-ins and auto-purges the nginx page cache on content changes (post/comment/update).

What is not shipped

  • Third-party Redis object-cache plugin — not needed: the Jabali Cache plugin IS the object cache (phpredis + persistent pconnect, installed by default fresh + on jabali update). Do not add a separate redis-cache plugin.
  • WP-CLI globally — wp is available to the install’s user via ~/bin/wp; not in $PATH for other users.

Other apps

Same wizard pattern works for the other 15 apps: Drupal, Joomla, MediaWiki, DokuWiki, phpBB, Flarum, OpenCart, PrestaShop, Moodle, ITFlow, InvoiceShelf, OpenEMR, osTicket, Nextcloud and PrivateBin. See applications.md.