[opensourcedex]

WordOps is a free, open source networking & connectivity project written in Python and released under MIT. It has 1,570 GitHub stars, 221 forks and 29 open issues, and was last pushed 2 months ago. On this registry it ranks #48 of 63 tracked projects in Networking & Connectivity, with 5 head-to-head comparisons available.

What is WordOps?

WordOps is a Python-based command-line tool for sysadmins and WordPress site owners who want to install and manage a full high-performance WordPress stack on a Debian or Ubuntu server with a few keystrokes.

What it is

WordOps is an open-source CLI, written in Python and released under the MIT licence, that automates the deployment and administration of a LEMP stack — Nginx, PHP, MariaDB and Redis — tuned for WordPress. It provides a single wo command that provisions server packages, provisions sites, issues SSL certificates and applies optimised Nginx configuration, plus a browser dashboard for server status, monitoring and tools. It is the successor path for users coming from EasyEngine, offering a one-step automated installer with migration from EasyEngine v3 support.

The concrete problem it solves is the manual, error-prone work of assembling and maintaining a performant WordPress server: installing and versioning Nginx, PHP-FPM, MySQL and Redis, writing hardened vhost configuration, wiring up page caching, and obtaining and renewing certificates. WordOps replaces that hands-on configuration with scripted commands such as wo site create example.com --wp, which installs the required packages and sets up WordPress, while its custom Nginx 1.30.4 build ships TLS v1.3, HTTP/3 QUIC and Brotli support out of the box.

Key capabilities

  • Fast, automated installation of WordPress, Nginx, PHP, MySQL and Redis, with a one-step installer and migration support from EasyEngine v3.
  • A custom Nginx 1.30.4 build with TLS v1.3, HTTP/3 QUIC and Brotli support, alongside strong cipher suites, modern TLS protocols and HSTS, reaching Grade A+ on SSL Labs.
  • Multiple cache backends selectable per site: --wpfc for nginx fastcgi_cache, --wpredis for nginx redis_cache, --wprocket for WP-Rocket, --wpce for Cache-Enabler and --wpsc for wp-super-cache.
  • WordPress multisite provisioning in both forms, via --wpsubdir for subdirectory installs and --wpsubdomain for subdomain installs, each combinable with any of the cache options.
  • Domain, subdomain and wildcard Let's Encrypt SSL certificates with DNS API support.
  • Current PHP version coverage from PHP 7.4 through 8.5 (selected with flags such as --php84), plus MariaDB 11.4 LTS and Redis 7.0.
  • Monitoring through live Nginx vhost traffic via ngx_vts_module, server monitoring with Netdata, and a WordOps dashboard showing server status and tools.

Who uses it and how

  • System administrators deploying production WordPress sites on Ubuntu 24.04 LTS (Noble) or Ubuntu 22.04 LTS (Jammy), the recommended platforms, with Debian 11, 12 and 13 also supported.
  • Operators running WordPress multisite estates who provision subdirectory or subdomain networks with a single command and choose a caching strategy per site.
  • Teams standardising WordPress hosting who want hardened security through strict Nginx location directives and optimised Nginx configurations across every site they manage.
  • Administrators migrating an existing EasyEngine v3 setup to a maintained successor using the automated installer's migration support.
  • Hosts serving non-WordPress workloads as well, using --html for static sites and --php or a version flag such as --php81 for plain PHP sites.

Getting started

Install with wget -qO wo wops.cc && sudo bash wo, then create your first site with sudo wo site create example.com --wp; further installation methods are covered in the documentation at docs.wordops.net.

How it compares

WordOps sits in the lineage of EasyEngine, whose v3 it directly replaces with a migration path, and it distinguishes itself through its custom Nginx build with HTTP/3 QUIC and Brotli, its explicit choice of cache backends per site, and its twice-yearly stable release cycle in June and December. Within this registry it is the tool named for automating a full WordPress-focused LEMP stack rather than general server configuration.

When to use it — and when not to

You should pick it only if you are comfortable operating a Linux server yourself, since WordOps stands up and leaves you responsible for Nginx, PHP, MariaDB, Redis, SSL certificate renewal and the monitoring services it installs; Windows hosts and non-Debian distributions are out of scope, and Raspbian is listed for testing purposes only. Note that stable releases arrive only in June and December, and there are 29 open issues, so plan for gaps between releases if you depend on bleeding-edge stack versions.

project readme (upstream, from github) — read inline

Wordops

An essential toolset that eases WordPress site and server administration

WordOps

CI MIT Commits GitHub release
PyPI - Downloads Badge Twitter

Key Features • Usage • RoadMap • Changelog • Credits • License

WordOps.net • Documentation • Community Forum • Dashboard demo

Key Features

  • Easy to install : One step automated installer with migration from EasyEngine v3 support
  • Fast deployment : Fast and automated WordPress, Nginx, PHP, MySQL & Redis installation
  • Custom Nginx build : Nginx 1.30.4 - TLS v1.3 HTTP/3 QUIC & Brotli support
  • Up-to-date : PHP 7.4, 8.0, 8.1, 8.2, 8.3, 8.4 & 8.5 - MariaDB 11.4 LTS & Redis 7.0
  • Secured : Hardened WordPress security with strict Nginx location directives
  • Powerful : Optimized Nginx configurations with multiple cache backends support
  • SSL : Domain, Subdomain & Wildcard Let's Encrypt SSL certificates with DNS API support
  • Modern : Strong ciphers_suite, modern TLS protocols and HSTS support (Grade A+ on ssllabs)
  • Monitoring : Live Nginx vhost traffic with ngx_vts_module and server monitoring with Netdata
  • User Friendly : WordOps dashboard with server status/monitoring and tools (demo)
  • Release cycle : WordOps stable releases are published in June and December.

Requirements

Operating System

Recommended
  • Ubuntu 24.04 LTS (Noble)
  • Ubuntu 22.04 LTS (Jammy)
Also compatible
  • Debian 11 (Bullseye)
  • Debian 12 (Bookworm)
  • Debian 13 (Trixie)
For testing purpose only
  • Raspbian 11 (Bullseye)

Getting Started

wget -qO wo wops.cc && sudo bash wo      # Install WordOps
sudo wo site create example.com --wp     # Install required packages & setup WordPress on example.com

Detailed Getting Started guide with additional installation methods can be found in the documentation.

Usage

Standard WordPress sites

wo site create example.com --wp                # install wordpress with [Current supported PHP release](https://endoflife.date/php) without any page caching
wo site create example.com --wp  --php84       # install wordpress with PHP 8.4  without any page caching
wo site create example.com --wpfc              # install wordpress + nginx fastcgi_cache
wo site create example.com --wpredis           # install wordpress + nginx redis_cache
wo site create example.com --wprocket          # install wordpress with WP-Rocket plugin
wo site create example.com --wpce              # install wordpress with Cache-enabler plugin
wo site create example.com --wpsc              # install wordpress with wp-super-cache plugin

WordPress multisite with subdirectory

wo site create example.com --wpsubdir            # install wpmu-subdirectory without any page caching
wo site create example.com --wpsubdir --wpsc     # install wpmu-subdirectory with wp-super-cache plugin
wo site create example.com --wpsubdir --wpfc     # install wpmu-subdirectory + nginx fastcgi_cache
wo site create example.com --wpsubdir --wpredis  # install wpmu-subdirectory + nginx redis_cache
wo site create example.com --wpsubdir --wprocket # install wpmu-subdirectory + WP-Rocket plugin
wo site create example.com --wpsubdir --wpce     # install wpmu-subdirectory + Cache-Enabler plugin

WordPress multisite with subdomain

wo site create example.com --wpsubdomain            # install wpmu-subdomain without any page caching
wo site create example.com --wpsubdomain --wpsc     # install wpmu-subdomain with wp-super-cache plugin
wo site create example.com --wpsubdomain --wpfc     # install wpmu-subdomain + nginx fastcgi_cache
wo site create example.com --wpsubdomain --wpredis  # install wpmu-subdomain + nginx redis_cache
wo site create example.com --wpsubdomain --wprocket # install wpmu-subdomain + WP-Rocket plugin
wo site create example.com --wpsubdomain --wpce     # install wpmu-subdomain + Cache-Enabler plugin

Non-WordPress sites

wo site create example.com --html     # create example.com for static/html sites
wo site create example.com --php      # create example.com with [Current supported PHP release](https://endoflife.date/php)
wo site create example.com --php81      # create example.com with php 8.1 support
wo site create example.com --php82      # create example.com with php 8.2 support
wo site create example.com --php84      # create example.com with php 8.4 support
wo site create example.com --php85      # create example.com with php 8.5 support
wo site create example.com --mysql    # create example.com with php 8.2 & mysql support
wo site create example.com --mysql --php83   # create example.com with php 8.3 & mysql support
wo site create example.com --proxy=127.0.0.1:3000 #  create example.com with nginx as reverse-proxy

Switch between PHP versions

wo site update example.com --php74 # switch to PHP 7.4
wo site update example.com --php80 # switch to PHP 8.0
wo site update example.com --php81 # switch to PHP 8.1
wo site update example.com --php82 # switch to PHP 8.2
wo site update example.com --php83 # switch to PHP 8.3
wo site update example.com --php84 # switch to PHP 8.4
wo site update example.com --php85 # switch to PHP 8.5

Sites secured with Let's Encrypt

wo site create example.com --wp -le #  wordpress & letsencrypt
wo site create sub.example.com --wp -le # wordpress & letsencrypt subdomain
wo site create example.com --wp --letsencrypt --hsts # wordpress & letsencrypt with HSTS
wo site create example.com --wp -le=wildcard --dns=dns_cf # wordpress & wildcard SSL certificate with Cloudflare DNS API

Update WordOps

wo update

Support

If you feel there is a bug directly related to WordOps, or if you want to suggest new features for WordOps, feel free to open an issue. For any other questions about WordOps or if you need support, please use the Community Forum.

Contributing

If you'd like to contribute, please fork the repository and make changes as you'd like. Pull requests are warmly welcome. There is no need to be a developer or a system administrator to contribute to WordOps project. You can still contribute by helping us to improve WordOps documentation. Otherwise, you can still contribute to the project by making a donation on Ko-Fi.

Sponsors

Thanks to our generous sponsors for supporting the development of WordOps:

Liquid Web
Liquid Web logo

Credits

Apps & Tools shipped with WordOps :

Third-party debian packages shipped with WordOps :

WordPress Cache Plugins supported by WordOps :

License

Frequently asked questions

Is WordOps free to use?

WordOps is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does WordOps do?

Install and manage a high performance WordPress stack with a few keystrokes

What is WordOps written in?

WordOps is primarily written in Python. Its source is publicly available at https://github.com/WordOps/WordOps, and it has 1,570 GitHub stars.