Your own Plone 6 website on a cloud server, without needing a command line.
Plone in a Box is for people who want a Plone site of their own but aren't system administrators. You fill in a form on your cloud provider's website (Linode, DigitalOcean, Amazon AWS or Hetzner), choose an admin password, and click Create. About 10 minutes later, the server's address shows your new Plone site, ready to log in and edit. There's nothing to install on your computer.
Behind the scenes, each box is a single Ubuntu 26.04 LTS server running the official Plone Docker images (the Plone backend, the Volto front end and PostgreSQL) behind nginx, with:
- the admin password you choose when creating the server, or a randomly generated one (never
admin:admin) - a page that shows setup progress while you wait, and turns into your site when it's ready
- only the website (HTTP and HTTPS) and SSH reachable from the internet
- optional HTTPS from Let's Encrypt when you give it a domain name
- all Ubuntu updates installed during setup, and swap added on small servers
Default versions: Plone 6.2 with Volto 19. Both are configurable; for the previous release line, use Plone 6.1
with Volto 18.
Pick a cloud provider. You'll need an account with them and a way to pay.
Which one? If you don't already use one of these, choose Linode: it has the simplest setup (a form with labelled fields, nothing to paste) and among the lowest prices for a small site. Choose DigitalOcean if you already have an account there; it costs about the same. Choose AWS if your organization already runs things there; its Launch Stack button opens a similar form, but a small site costs noticeably more. Choose Hetzner if you prefer a European provider; it costs about the same, and setup works like DigitalOcean's. The setup guide compares them.
A 1 GB server is enough for a small site on Linode, DigitalOcean and Hetzner (choose 2 GB or more for a busier one);
on AWS, use at least t3.small (2 GB).
The setup guide has step-by-step instructions for each provider.
- Log in to Cloud Manager, open the Plone in a Box StackScript (by nguyen-plone), and click Deploy New Linode.
- Fill in the form. Set the Plone admin password (at least 12 characters); the domain name, time zone, versions, backend add-ons and a theme are optional.
- Choose Ubuntu 26.04 LTS (24.04 also works), a region and a plan (a 1 GB Nanode is enough for a small site), set a root password, and pick No firewall if Cloud Manager asks for one (the server has its own).
- Click Create Linode, then open the Linode's IP address in your browser.
Details: setup guide, Linode.
- In the DigitalOcean control panel, Create → Droplets: choose Ubuntu 26.04 (LTS) x64 and a size (1 GB is enough for a small site).
- Under Additional Options, choose Startup scripts (free) and paste these three lines into the box. Replace
CHANGE-MEwith your admin password (at least 12 characters), keeping the quotes:#!/bin/bash export ADMIN_PASSWORD='CHANGE-ME' curl -fsSL --retry 10 --retry-all-errors -o /root/plone-in-a-box.sh https://raw.githubusercontent.com/tkimnguyen/plone-in-a-box/2.11/src/StackScript && bash /root/plone-in-a-box.sh - Create the Droplet, then open its IP address in your browser.
For more settings (a domain for HTTPS, the time zone, versions, add-ons, a theme), paste src/user-data.sh instead.
Details: setup guide, DigitalOcean.
- Sign in to the AWS console, then click
- Fill in the form: set the Plone admin password (at least 12 characters); everything else is optional.
- Click Create stack. When it shows
CREATE_COMPLETE(a minute or two), open the SiteURL on its Outputs tab.
Details: setup guide, AWS console.
- In the Hetzner Console, open a project and click Create server: choose a Regular Performance plan (CPX02, 1 GB, is enough for a small site; CPX11 in the US), a location and Ubuntu 26.04.
- Under Cloud config, paste these three lines into the "Cloud-init configuration" box. Replace
CHANGE-MEwith your admin password (at least 12 characters), keeping the quotes:#!/bin/bash export ADMIN_PASSWORD='CHANGE-ME' curl -fsSL --retry 10 --retry-all-errors -o /root/plone-in-a-box.sh https://raw.githubusercontent.com/tkimnguyen/plone-in-a-box/2.11/src/StackScript && bash /root/plone-in-a-box.sh - Click Create & Buy now, then open the server's IPv4 address in your browser.
For more settings (a domain for HTTPS, the time zone, versions, add-ons, a theme), paste src/user-data.sh instead.
Details: setup guide, Hetzner.
-
Log in as
adminwith the password you chose. For everyday editing, create personal accounts in Site Setup → Users and Groups. -
Forgot the password, or didn't set one? Your provider has a console that runs in the browser: Linode's Launch LISH Console, DigitalOcean's Access → Launch Droplet Console, AWS's Connect → EC2 Instance Connect, or Hetzner's Console (the
>_button on the server's page). Open it and type one command:sudo cat /root/plone-credentials.txtshows a generated password, andsudo plone-reset-admin-passwordsets a new one. -
Using your own domain name: point the domain at the server's address before creating it, and fill in the domain and email settings to get HTTPS automatically. Adding a domain to an existing server takes a few commands; see Adding HTTPS later.
-
Removing the site: delete the server in your provider's control panel. This deletes the site's content too.
-
Add-ons: backend add-ons such as
collective.easyformcan be installed when deploying, or later; see Add-ons. -
Volto Light Theme: set the frontend image to
ghcr.io/collective/plone-in-a-box-frontend:19-vltwhen deploying; see Themes and frontend images.
The setup guide also covers backups, upgrades and troubleshooting.
AWS, DigitalOcean and Hetzner can also be set up with Terraform from src/aws/,
src/digitalocean/ and src/hetzner/. They run the same
provisioning script as the console routes,
src/StackScript, which is also the Linode StackScript.
cd src/aws # or src/digitalocean with DIGITALOCEAN_TOKEN set, or src/hetzner with HCLOUD_TOKEN set
terraform init
terraform apply -var 'ssh_public_key_path=~/.ssh/id_ed25519.pub' -var 'admin_password=...'
See the variables at the top of each main.tf for region, size, domain, versions and
backend add-ons, and the
setup guide for account setup. Pass the same -var options to
terraform destroy, or put them in terraform.tfvars. If Terraform fails with
lookup sts.<region>.amazonaws.com: no such host on a Mac, turn off iCloud Private Relay and retry.
On the server (ssh root@<server>, or ubuntu@<server> and sudo -i on AWS):
- setup is logged to
/var/log/plone-in-a-box.log, and a generated admin password is saved in/root/plone-credentials.txt - the stack lives in
/opt/plone; manage it withdocker compose --project-directory /opt/plone ps|logs|pull|up -d - to add a domain later, point its DNS at the server and run
certbot --nginx -d <domain>
Development and releases happen at tkimnguyen/plone-in-a-box, which is mirrored to collective/plone-in-a-box after each release. Release notes are on the Releases page, and CHANGES.md lists the changes in every version. Both repositories have the same version tags.
Maintainers: see RELEASING.md for testing (including automated test deploys), releasing and syncing
to collective/plone-in-a-box.
The original step-by-step guide from the 2020 Plone Conference (PDF,
markdown) describes the Plone 5.2 version; the account
setup steps still apply, but the port 8080 and admin/admin instructions no longer do.
See the accompanying 2020 Plone Conference presentation, Your Plone [Intranet] in a Box™:
