About Services Tools Blog Contact us

Directory Live Sync

Copies improved listings and images from a private working database to the live directory, and stops if the secure connection is down.

  • Scheduled Workers & Sync
  • Leisure and sport
  • Scheduled worker
  • Product
  • Hybrid
  • 2026

The problem

Improvements made on a laptop do nothing until the public directory shows them. Writing to the live site straight from an experiment is unsafe. Sending the same batch twice makes duplicates, and a half-sent batch after a dropped connection is worse than none.

What it does

The copy tools send a limited batch of improved listings, then images, then related places. They stop if the secure connection is not open. Each batch is saved on the live side all or nothing, and each row sent is recorded in a local list so it is not sent twice. The public site keeps reading the same data as before.

Outcomes

  • The public directory shows improved entries and reads its data as before.
  • A closed connection stops the run before anything is written.
  • An entry is never sent twice.
  • The sent list records what moved.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Live sync

tunnel open
Tunnel 3307
Open
accepting connections
This batch
10
listings, then images, then places
Already in the log
0
duplicates will be skipped
Listings 10 waiting
Chalk Pit Centre Maidstone
Harbour Steps Brighton
Mill Lane Hall Canterbury
+ 7 more in this batch
Images 8 waiting
chalk-pit-hall.jpg
harbour-steps.jpg
+ 6 more
Places 4 waiting
Station yard Maidstone
River path Canterbury
Hill car park Sevenoaks
Lane campsite Ashford
Seeder
One transaction. The public site keeps its current tables.

Tunnel down

port closed
Tunnel 3307
Closed
not accepting connections
Local queue
22
still on the laptop
Live writes
0
abort comes first
Listings
10 enriched rows waiting
Images
8 files waiting
Places
4 related places waiting
Preflight
A half-written batch is worse than no push.

Local push log

source of truth
Rows moved this week
History
WhenQueueRowResult
09 Oct 18:04ListingsChalk Pit Centrecommitted
09 Oct 18:04Imageschalk-pit-hall.jpgcommitted
09 Oct 18:05PlacesStation yardcommitted
08 Oct 11:12ListingsMill Lane Hallduplicate
07 Oct 16:40ListingsHarbour Stepscommitted
07 Oct 09:02Tunnelport 3307aborted

How it works

  1. Check the secure connection and stop if it is closed.
  2. Send a limited batch of improved listings, saved all or nothing.
  3. Send images, then related places.
  4. Record each success in a local list of what was sent.
  5. Skip entries already on that list.
  6. Leave the public site reading the data it already uses.

Pipeline

flowchart LR
  Local["Local rows"] --> Tunnel{"Tunnel open"}
  Tunnel -->|no| Abort["Abort"]
  Tunnel -->|yes| Push["Transactional push"]
  Push --> Live["Live tables"]
  Push --> Log["Push log"]