Trellis's install command lives on another website
WordPress LEMP stack with PHP 8.3, Composer, WP-CLI and more
At a glance
- What is it?
- Trellis is a set of Ansible playbooks that build a LEMP stack for WordPress, and the page describing it contains no command, no playbook name and no configuration example. Installation is one link, the requirements file asks for a single dependency, the tests are Python, and the repository has moved five months past its newest release tag.
- Who is it for?
- Trellis suits a team already using Ansible to run WordPress, who want Bedrock based sites deployed with a rollback path and who can host their own virtual machines. Before adopting it, read the installation documentation rather than the repository page, because the page cannot tell you how the thing is invoked, and check that your Ansible version satisfies the only stated requirement.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 10 days ago.
- What is it written in?
- Mainly Jinja, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- roots/trellis2,585 ★ · +3
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| roots/trellis | 2.6k | 2.6k |
3 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The page that describes the project contains no command
Read the whole page and there is not one thing to type. The overview is four bullets, the getting started section is one sentence whose entire content is a link to the installation documentation on the project site, and there is no code block anywhere on it. So a reader arriving from a search for this project learns that it is an Ansible powered LEMP stack for WordPress, that it does local development with Lima virtual machines, that it targets high performance production servers, that it does zero downtime deploys for Bedrock based sites, and that a separate command line tool exists for management. What it does not learn is the name of the command, which playbook to run first, what a project directory looks like, or how a new site is created. Every one of those lives on the documentation site, which means the repository cannot be evaluated from itself.
Six playbooks, three of which are the lifecycle
The root tells you what the project actually runs. There is a server playbook for provisioning, a deploy playbook, a rollback playbook that is its own file rather than a flag on deploy, and a development playbook. Then two more that are utilities rather than stages: one that checks variables, and one dedicated to an Xdebug tunnel. Around them sit the standard Ansible furniture, a configuration file for the tool itself, a group variables directory, a hosts directory, a `lib/` directory for custom filters and modules, a public keys directory, and a `deploy-hooks/` directory for things that run at deploy time. Reading the names in order gives you the whole story of the tool's shape: build the machine, ship the code, undo the ship, develop locally, and two side channels for checking and for debugging.
The requirements file has one line and the tests are Python
The dependency declaration is as short as it gets:
ansible>=2.10.0One requirement, a lower bound rather than a pinned version, and nothing else. That is the entire runtime dependency of a project whose job is to configure a stack containing PHP, a database and a web server, which tells you the rest arrives on the target machine rather than from this repository. Alongside it there is a separate development requirements file, a pytest configuration file and a `tests/` directory, so the project's own test suite is Python even though the code it tests is Ansible playbooks and Jinja templates. The primary language of the repository is reported as Jinja, which is consistent: the playbooks are mostly templates, and the templates are mostly Jinja.
It is a Galaxy role, a CLI config and a project type all at once
Three files in the root describe how the project is meant to be consumed. There is a Galaxy metadata file, which is the manifest Ansible uses to publish a role to its own registry, so this stack can be pulled in the way other roles are rather than only cloned. There is a configuration file for the separate command line tool, the one the overview points at as being for easier management, which lives in its own repository and is therefore versioned independently of the playbooks. And there is a dot directory named after the project itself, which is where a project type's own settings live, the kind of file that decides what scaffolding options a new site is offered. Three distribution shapes for one stack: a role, a CLI, and a project template, each with its own release cycle.
Local development means a virtual machine, not a container
The local environment is described in one line as Lima virtual machines, and that choice has consequences the overview does not spell out. A virtual machine means the playbook set runs against something with its own kernel, its own service manager and its own package manager, which is closer to production than a container would be and slower to start than one. The Xdebug playbook in the root is the tell: debugging PHP inside a virtual machine needs a tunnel to reach the interpreter from your editor, and that is what the extra playbook is for. So the development path and the deployment path are meant to be the same playbooks against two kinds of machine, which is the design's strength and also the reason the repository carries a debugging playbook at all.
Sponsoring is the door to the chat, and a sponsor link carries an identifier
The support section explains the funding model and then attaches access to it. Roots describes itself as an independent open source organisation supported only by developers, says that sponsorship funds a separate package project and the wider ecosystem, and states that sponsors get access to a private Discord channel. The community section repeats the same condition from the other direction: to join the Discord, sponsor on GitHub. Public community is therefore split, with a Discourse forum, a Twitter account, a blog and a newsletter open to anyone, and the chat gated. The sponsor row underneath lists four companies as links, and one of those four carries a query string with an identifier in it, the shape of a referral link rather than a plain sponsorship acknowledgement.
Five months past the newest tag, with a stray tag in the header
The release history and the branch are not aligned. The three most recent tags are v1.31.1 on 2026-04-15, v1.31.0 on 2026-04-09 and v1.30.0 on 2026-03-18, while the default branch was last pushed to on 2026-09-18. So the tree you would clone is roughly five months ahead of the newest published release, and the version file at the root is the other place a version number lives, alongside the tags. The page carries a version file, a licence file and a continuous integration badge pointing at a workflow named for continuous integration, and the header line describing the project closes with a closing emphasis tag that has no matching opening tag anywhere in the same line. None of that changes what the project does, but it does mean the page is maintained by hand in places where a generator would be safer.
Editorial conclusion
Trellis suits a team already using Ansible to run WordPress, who want Bedrock based sites deployed with a rollback path and who can host their own virtual machines. Before adopting it, read the installation documentation rather than the repository page, because the page cannot tell you how the thing is invoked, and check that your Ansible version satisfies the only stated requirement. Decide early whether you want the Lima based local development path, since that is the piece with extra moving parts and its own debugging playbook. And if you are evaluating the project by its releases, note that the newest tag predates the last commit by months, so the branch you would actually install from is ahead of what the release history describes.
Frequently asked questions
What is roots/trellis?
It is a collection of Ansible playbooks for setting up a LEMP stack for WordPress, published under the MIT license with the newest release at v1.31.1. The overview lists a local development environment built on Lima virtual machines, production server provisioning, zero downtime deploys for Bedrock based WordPress sites, and a separate command line tool for management.
How do I install Trellis?
The page does not say. Its getting started section is one sentence pointing at the installation documentation on the project site, and no command appears anywhere on the page. The repository's own dependency declaration is a single line, ansible>=2.10.0, with a separate development requirements file beside it.
Which playbooks does Trellis ship?
A server playbook, a deploy playbook, a separate rollback playbook and a development playbook, plus two utilities: one that checks variables and one that sets up an Xdebug tunnel. They sit alongside an Ansible configuration file, group variables, a hosts directory, a lib directory for custom filters and modules, a public keys directory and a deploy-hooks directory.
How do I develop a Trellis site locally?
The overview describes a local development environment built on Lima virtual machines, and the repository carries both a deploy-hooks directory and a dedicated playbook for an Xdebug tunnel, which is how you reach the interpreter in a virtual machine from an editor. No local setup command appears on the page itself.
How does Trellis test itself?
With Python tooling: the repository holds a pytest configuration file, a tests directory and a separate development requirements file, while the runtime requirements file contains only ansible>=2.10.0. The code under test is Ansible playbooks and Jinja templates, and the primary language of the repository is reported as Jinja.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/roots-trellis)Star history chart for your README
[](https://hysenlabs.com/projects/roots-trellis)Was this useful?