Running Magento 2 with Govard: one command, production-shaped

This whole Magento 2 series assumes a production-shaped stack. Here's how Govard delivers it without hand-written Dockerfiles.

The problem it solves

Magento 2 local setups drift from production: opcache off, files session, no Varnish, SQLite search. Bugs surface only after deploy. Govard treats the environment as a first-class concern.

The shape it builds

A single bring-up wires the topology this series has described throughout: Nginx (pointed at pub/), PHP-FPM, MariaDB, Redis 7.4 (sessions + cache), Varnish 8.0 in front, and OpenSearch 3.0 for search. That's the same layered cache and search topology from the performance and cache posts.

The workflow

govard env up        # builds the stack
govard shell         # drops into the Magento root
bin/magento setup:upgrade

No Dockerfile to maintain; the framework awareness keeps env.php, table prefix, and service wiring in sync — which is why the anatomy and EAV posts could describe env.php as managed, not hand-edited.

Why it matters for this series

Every "run it locally" note in the prior posts — profiling upgrades, testing on a real stack, exercising B2B APIs — assumes this shape. Govard is the concrete implementation of "production-shaped local."

What's next in this series

The final piece: a pragmatic observability setup so you can see a Magento 2 store the way the audit checklist expects.

Next in this series: Magento 2 observability — /blog/magento2-observability