The KamalCloud app is down for maintenance. Sign-ups and sign-ins are paused.App down for maintenance. Sign-ups paused. Details
Template
The site builder and blog, with its plugins and themes, backed by MySQL. It installs as an ordinary app that deploys, backs up and rolls back like yours.
Installing does not deploy. Point an A record for the domain at the server, then press Deploy.
A registered server and a ready runner.
A hostname, if you have one. WordPress writes its site address into the database the moment its installer runs, so pointing the domain first is less work than changing it after.
Somewhere off the machine for backups. Two things hold state here -- the database and wp-content -- and they are backed up separately.
Change the image tag on the app and deploy. Core comes out of the pinned image on every boot, so the tag is the version that runs. Don't upgrade from the dashboard: wp-config.php is rewritten at each boot, so an update made there is undone by the next deploy.
Yes. Those live in the wp-content volume, which survives a redeploy, so they update from the dashboard as usual. Only core is pinned to the image.
A MySQL accessory on the same machine, reached by its container name on the kamal network and never published outside it. Its dumps are backed up like any accessory's.
Not out of the box. The image sends through PHP's mail(), which is not configured in the container, so use an SMTP plugin with a relay or your mail provider's submission port.
No. TLS is kamal-proxy's, and the image already trusts its X-Forwarded-Proto, so WordPress builds https links behind it without a wp-config change.
Connect a server, install WordPress, and deploy when the domain points at it.
Sign-ups are paused while the app is in maintenance.