GLWS · Web publishing
Publish a blog, business site or content-heavy website with a familiar content management system.
Common uses of WordPress.
Choose supported PHP and database versions, enable HTTPS and review the requirements of the themes and plugins you intend to use.
Planning examples, not official minimum requirements.
Web publishing
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the WordPress documentation ↗ (opens in a new tab)Advice specific to this application.
A WordPress site includes the web server, PHP workers, a database and uploaded media. Plan around the busiest page types and simultaneous visitors. A cache can reduce repeat work, while commerce, search and membership plugins can change memory and database demand.
Record the active themes and plugins, retain a database backup together with the uploads and configuration, and test changes before applying them to your main site. A complete recovery needs both the content and the settings that connect it to the database.
Linux guides that help with this setup.
Set up Nginx, PHP-FPM and MariaDB, download and verify WordPress, secure its files and finish with HTTPS.
Read guide →Follow a request from Nginx to your application, read the error log, check ports, services, SELinux and timeouts and fix the common causes.
Read guide →Back up to a second server over SFTP with restic, encrypt everything, schedule it with a systemd timer and prove you can restore.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name wordpress
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Build an independent publication with posts, newsletters and membership tools.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →