Menu

How I keep every client site in one repo (and deploy them all from one place)
📰

How I keep every client site in one repo (and deploy them all from one place)

DEV Community: productivity·Linc·2 days ago
#fNjPHsGw
#devtoproductivity#devto#dev#client#every
Reading 0:00
15s threshold

When I was on WordPress every client site lived somewhere different. Two on SiteGround, one on a cheap cPanel box the client bought themselves, a couple on WP Engine. Every login was a seperate password reset waiting to happen.

After moving most of them to Astro I put every client site in one repo. It sounds like a small thing but it changed how I run the whole agency, so here is the setup.

The folder layout

Nothing clever. One folder per client, each one is a normal Astro project:

clients/ bakery-surry-hills/ physio-newtown/ plumber-parramatta/ ... shared/ components/ checks/ AGENTS.md sites.json

Enter fullscreen mode

Exit fullscreen mode

I use pnpm workspaces so shared/components (footer, contact form, cookie free analytics snippet, schema helpers) gets imported by every site. When I fix the footer once, every client gets it on the next deploy.

I did try one repo per client for a while. It was fine at 5 sites and a mess at 15.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.