LIVE MEETS GITHUB

Same
as
GitHub?

First published

I upload most of my sites by hand, one file at a time. So every night the network asks a simple question: is what's live the same as what I built? It asks GitHub first, and only knocks on the host's door when something has really changed.

See how it checks
The version check
  • Has GitHub changed?Every night
  • Then: read that siteOnly if so
  • Every site, read in fullFriday morning
  • Everything matchesSilence
  • Something doesn'tOne ticket
Ask the cheap question first.
01 / OVERVIEW

Overview

Every file I change carries a version number, and GitHub holds the latest of each. The version check compares the two for every site and every app in the network, and shows the answer as one light per site in Monty Control.

It runs by itself every night. It doesn't scan every site to do it: it asks GitHub what has changed first, and only reads the sites where something has.

This case study covers why the check exists, how it avoids leaning on the host, what the lights mean, and why it stays silent unless something is wrong.

02 / AT A GLANCE

The Check at a Glance

One question every night, one light per site, one ticket only when it matters.

19Sites and subdomainsEvery one in the network's master list
8AppsEach compared with its version on GitHub
00:30Every nightClear of the other night jobs, Polish time
0Tickets when it all matchesRoutine checks write nothing at all

These figures cover only the sites and apps in the version check, not every site and app in the network, so other case studies may show different numbers.

Version stampsGitHub firstOne light per siteFile by fileWaiting to uploadApps checked tooFriday sweepTickets on mismatch only
03 / PERSONAL STORY

Why I Built It

I upload to my host the careful way: back up the site, rename the old file, upload the new one. One file at a time. It's safe, but after a long day at the laptop I couldn't always say for certain that every file had gone up, or which version of a page was really live.

A missed upload doesn't announce itself. The site keeps working, just with yesterday's file. I wanted to know, without having to remember, and without checking each site by hand.

The question I wanted answered.

Is what's live the same as what I built? Yes or no, for every site, every morning.

04 / THE CHALLENGE

The Challenge

Comparing two copies of a website sounds simple. The details make it interesting:

  • most sites live on a shared host and are uploaded by hand, file by file
  • a file can be changed on the host directly and never reach GitHub
  • the newer sites deploy themselves from GitHub, so they can't drift at all
  • the Android apps are built and installed by hand, on Tuesdays
  • a shared host doesn't like being asked lots of questions at once
  • and the key that reads GitHub must never sit inside the control panel
05 / EVERY FILE HAS A NUMBER

Every File Has a Number

Every file I change carries a small stamp near the top: its version, and the ticket that changed it. The number goes up by one with every change and never goes backwards.

  • On the live site, a small private page reports every stamped file, its version and a fingerprint of its contents.
  • On GitHub, the same file has the same fingerprint when it's the same file, to the last character.
  • The ticket that made a change lists every file and its new version, so an upload can be checked off against the live site.

Same fingerprint, same file. A higher number on GitHub means it's waiting to be uploaded. The same number with a different fingerprint means someone changed it on the host.

06 / ASK GITHUB FIRST

Ask GitHub First

The first version of the check read every site, every time. On its very first day the host politely asked it to slow down. Fair enough: reading a whole site to find out nothing has changed is a lot of work for no news.

So I turned it round. GitHub knows when a project last changed, and asking it costs almost nothing. Now the check works like this:

  1. AskHas this site's project changed on GitHub since I last looked?
  2. SkipNo change, and it matched last time? Leave the host alone
  3. ReadChanged, or files still waiting? Read that site, file by file
  4. ReportEvery site gets its light, with the date it was last read

On a normal night the host isn't asked anything at all. After a day of building, only the sites I worked on are read. When the host does say "slow down", the check stops there and picks up the rest later, rather than pressing on.

The reading itself is done by the network's own AI gateway, Monty MCP, which runs on Cloudflare and keeps the only key to GitHub. Monty Control simply asks it and shows the answer.

07 / ONE LIGHT PER SITE

One Light per Site

The Versions page in Monty Control shows the whole network on one screen, on the laptop, the phone or the tablet.

LightWhat it means
GreenSame as GitHub, or the site deploys itself from GitHub
AmberFiles waiting to upload, or a file that needs a look
GreyNot read yet this time, or still reading
  • Tap a site to see every file: its live version, its GitHub version and the ticket that last changed it.
  • Waiting to upload gathers every file across every site into one list: my laptop to-do, in one place.
  • Check this site again reads one site straight away, which is how I confirm an upload.
The Versions page in Monty Control on a tablet: 19 sites the same as GitHub, nothing to upload, nothing needing a look, and one app to rebuild
The top of the Versions page: 19 the same as GitHub, nothing waiting, and on this refresh 12 host sites left alone because GitHub hadn't changed.
The Sites list on the Versions page: each site with a green light, the Cloudflare sites marked Deploys from GitHub and the host sites marked Same as GitHub with the date they were last read
One light per site. Private addresses are blurred.

The same light sits on the Health card of Monty Control's dashboard, so I see it without opening anything.

08 / THE APPS

The Apps

Apps are different. I build them from GitHub in Android Studio on Tuesdays and install them myself, so whatever GitHub says is, by the end of Tuesday, what's on my phone.

  • Built from GitHub: for most apps, the version on GitHub counts as the installed one.
  • Reporting for real: the Monty Social app tells the sites its version each time it opens one, so it's checked for real, and shows "Rebuild Tuesday" when GitHub is ahead of it.

Asking every app to report itself would have meant changing and rebuilding all of them, to learn something I already knew. I left it out on purpose.

09 / THE NIGHT SHIFT

The Night Shift

The check runs from Monty Cron, my own scheduling service, on two timetables:

Every night, 00:30

  • GitHub first, as above
  • Only the sites that changed, or have files waiting, are read
  • Set to stay clear of the stats collectors and the other night jobs

Friday morning, 06:00–07:50

  • Every site read in full, two at a time, every ten minutes
  • Catches the one thing GitHub can't see: a file changed on the host
  • Finished well before my weekly ticket review at 13:00

Spreading the Friday sweep over two hours means the host never gets a burst of questions, and the whole network is still read in full once a week.

10 / A TICKET ONLY WHEN IT MATTERS

A Ticket Only When It Matters

A routine check that finds nothing writes nothing. No ticket, no message, no log to read. I only hear from it when a version doesn't match and nothing already explains why:

  • Changed on the host
  • Live newer than GitHub
  • Live but not in GitHub
  • Waiting, ticket closed
  • Waiting, no ticket
  • A file waiting to upload with its job still open is not a problem: its own ticket already explains it.
  • One ticket per site, listing each file, what's wrong and the steps to put it right, in the same Ticket Method style as every other job.
  • Never twice. The same mismatch isn't reported again while its ticket is open.
11 / RESULTS

Results

The version check went from idea to running every night in a single afternoon, and on its first evening every site in the network matched GitHub.

19 / 19Sites matching GitHubOn the first full evening
8 of 10Host sites left aloneOn a refresh where GitHub hadn't changed
1AfternoonFrom the first idea to running every night

The best moment came on day one. A finished upload showed up as green within seconds, and a file I'd built minutes earlier showed up amber, waiting, before I'd even reached the laptop.

Figures as of 14 November 2026, from Monty Control. These figures cover only the sites and apps in the version check, not every site and app in the network, so other case studies may show different numbers.

12 / WHAT'S NEXT

What's Next

  • Every file stamped, in time. Older files get their number the next time a job changes them, so the check sees more of each site week by week.
  • New sites join on day one. A site added to the master list is checked the same night.

Read more

What I've learnt

Ask the cheap question first. Most nights the honest answer is "nothing has changed", and it shouldn't take a whole website's worth of work to hear it.

Built by hand. Checked every night.

Built for my own network — this isn’t a public product. Want to know your live sites match what you built? I build bespoke.

Contact us ↗