hubshop-env

Healy sells into markets that share almost nothing on the operations side — the EU, the US, Japan, Korea, India, Australia, Canada, Mexico, Colombia, Thailand and the wider Asian region each have their own storefront on a shared WooCommerce core. The platform team's problem was not building them. It was working on them day to day.

The old workflow ran one region at a time. Switching meant stopping the stack, starting another, and importing a database. That took fifteen minutes, several times a day, every time a bug report named a different market. Hosts were edited by hand, certificates were per developer, and there was no way to run the tests.

hubshop-env is a fork of WordPress's own wp-env, rebuilt so many regions can run together. They all run at once, so switching is just a different URL, not a wait. DNS is wildcard through dnsmasq and certificates come from mkcert, so a new region needs no sudo and no manual trust. Setup went from twenty minutes to under ten.

The rest is what a platform team asks for once the basics stop hurting: Xdebug and SPX profiling behind flags, a dedicated test container so PHPUnit has somewhere to run, a `doctor` command that checks Docker, DNS, SSL and port problems instead of leaving you to guess, sync that lets you pull a database without five gigabytes of uploads, git worktree support so two branches run side by side, and a one-command Cloudflare tunnel to show someone your local environment without an ngrok account.