I build and run the platform under Magento and Adobe Commerce stores: the infrastructure, the release pipeline, and the tooling that proves a deploy worked before a customer finds out it didn't. I've been working in Magento since the 1.x days.
Most of my day is PHP, Python and Ansible. I'm ramping up in Go, Rust and Ruby.
- manipulus works out which RequireJS modules each Magento 2 page type loads, straight from the codebase, and bundles them. No browser, no Node, no running store. Its walkthrough takes a stock 2.4.8 store from 226 JavaScript requests to 15.
- section-policy decides what a private-content invalidation actually invalidates, and reports what each action costs. On a stock store, logging in refetches every customer section, including a country list of around 59 KB that's identical for every visitor.
- cache-vary decides what goes into the full-page-cache key, and reports how many copies of each page it allows. It keeps customer segments out of the Varnish hash when nothing cached depends on them, since each active segment can double the copies of every page.
- process-guard times every observer on the hot paths (order placement, totals, catalogue saves, queue consumers) and sheds the ones declared advisory when a path goes over its budget.
- catalog-access does the catalogue reads every module ends up writing (load a product, turn category ids into names, work in the right store) in batches, with the usual mistakes designed out, like one product loaded per loop.
- catalog-index serves category, search, product and GraphQL pages from OpenSearch documents that stay current within seconds, while the database still decides checkout. It's not released yet.
- catalog-batch asks for configurable product data once per page instead of once per product, with no index and nothing stored. It's not released yet.
- promotion-access answers the cart price rule questions every module ends up asking, like a rule's action or the rule behind a coupon, in batches and without loading a rule for each one.
- foundation and logger are the shared pieces the modules above are built on.
- Every released module above installs from one Composer repository, packages, and brings the modules it needs along with it.
- bluetir drives a real browser through a storefront, adds to cart and places an order. Luma, Hyvä and ScandiPWA are each one YAML profile, so a new store means a new profile rather than new code.
- drexbot runs regression, acceptance, behaviour and performance tests against a Magento storefront.
- harness-kernel is the test kernel drexbot is built on. It knows nothing about Magento: it owns the run, the verdicts and the reports, so it can back a harness for anything.
- emporion runs a Magento 2 store on your machine as a Docker Compose stack or a kind cluster, from one image. A second store, with its own database, cache, search index and queue, is one command.
- kapelos is emporion's smaller sibling: one Magento 2 store on your computer with Docker Compose, started from nothing or from a store you already have. Your code stays where it is, so an edit is live in the store straight away.
- healthbot checks whether customers can actually buy. Every five minutes it drives a real browser through search, cart and checkout, folds in New Relic, Google Analytics and CloudWatch, and decides whether anyone needs waking up. It ships its own Terraform, Packer and Ansible, and a local stack that runs the production code path with no credentials.
- credential-guard keeps credentials out of git. It scans the working tree and every blob in the history, and installs itself as a pre-commit hook.
- dep-intel tells you which of your dependencies are vulnerable without telling anyone what you run. It matches OSV and CISA's list of exploited vulnerabilities offline, across nine ecosystems.
- ansible-role-devops sets up a DevOps workstation, or creates and hardens an automation account on a server, on Ubuntu, Debian, Fedora and RHEL 9.
- dev-snapshot makes one encrypted, verified archive of a source tree, leaving out everything a package manager can rebuild.
- tooling-sync tells an installed command apart from the repository it came from, and shows which one changed.
- magento-deploy-playbook builds a Magento 2 release on a builder host, pushes it to a fleet, switches over and prunes what it replaced. A build lock stops two people cutting the same environment, and a throwaway Docker fleet lets you watch a whole deploy without owning a server.
- terraform-aws-modules is a library of Terraform modules for AWS, from multi-account setup and networking to data, edge and identity, with worked examples that put them together. Its guide takes you from a clone to a planned stack without an AWS account.
- periodic-journal handles every recurring note from one list of note types, instead of five fixed ones. A second daily note is just another entry.
- stickies puts movable sticky notes on a passage. They follow the text as it's edited and never touch the Markdown.
- world-engine validates a structured vault against YAML schemas and checks it for continuity, with the notes staying the source of truth.
- engineering-toolkit adds light structure to the engineering docs a vault already holds: ADRs, incidents, infrastructure notes and a decision log.
- jira-autolink turns
PROJ-123into a link to your Jira, with an optional hover preview of the issue.
- ordane is a desktop console for an Ansible control plane, with or without a Makefile. It shows the exact command before it runs, streams the output and keeps a record of every run, with no server and no database.
- backsight is a Terraform workbench that shows what a change will do while you write it. It's early and not released yet.
- solander opens an Obsidian vault on Ubuntu and never writes into it. Wikilinks, callouts, canvases and Dataview render as themselves, with no plugins, no scripts and no network.
- ariadne builds a book's cast as you read and never shows you anyone past your bookmark. It works offline on epubs you own. It's early, and it needs readers.
- cairn keeps every job application you're chasing in one list and screens the job feeds you turn on against what you want. Everything stays in one encrypted file on your machine: no account, no server, no sync.