01 / THE SOURCES
Weather on the ground.
WeatherLink brings in local observations. The homepage uses East Cliff at Pennard; dedicated dashboards also show Mumbles and Llansamlet.
Explore local weatherBEHIND THE LOCAL LINE
A little local knowledge, with a new engine behind it. Here’s how Gower Live brings the coast to your screen.
THE NEW SETUP
The new website replaces WordPress with Astro on Cloudflare Workers. Pages bring together shared readings from a Cloudflare D1 database; camera video travels directly from its provider to your browser.
01 / THE SOURCES
WeatherLink brings in local observations. The homepage uses East Cliff at Pennard; dedicated dashboards also show Mumbles and Llansamlet.
Explore local weather02 / THE SOURCES
The South Pembrokeshire buoy supplies offshore wave height, period and direction through Cefas WaveNet. These readings describe the buoy location, rather than surf at a particular beach.
See buoy readings03 / THE SOURCES
Swansea tide predictions are combined with Mumbles sunrise and sunset times to show daylight water windows. Predicted height is different from measured water depth.
Check water access04 / THE SOURCES
Two views, delivered directly by Ozolio. Bay and Waterfront use their own video proportions, with playback handled by the camera provider.
Watch the bayFRESH READINGS. LESS REPEATED WORK.
Scheduled Workers fetch the feeds once for everyone. A shared snapshot and a short cache help keep pages fast without asking the source for every visit.
While a page is visible, it checks for updates once a minute. Checks pause in a hidden tab and resume when you return.
THE TIME ON THE READING MATTERS
An import or page refresh never makes an old observation new. Weather readings are marked stale after 15 minutes; buoy and air-quality readings after 90 minutes. Missing readings stay unavailable.
Tides are predictions. The hourly report is a factual summary of the stored data. The experimental Mumbles Downwinder meter uses Pennard gusts, with separate wind-direction, water and daylight checks. None of these replaces checking conditions on the water.
Read the latest reportContent and code are maintained through Git. Data-source attribution is included in the footer.
THE CLOUDFLARE SETUP
Two Workers. One shared database. Here’s what does what.
01 / THE WEBSITE
One Worker runs the Astro website, renders pages and serves the data and calendar endpoints. A second Worker handles scheduled imports and the hourly report, independently of visits.
02 / THE READINGS
Both Workers connect to the same SQL database. It holds weather, buoy and air-quality observations, tide predictions, reports and import results. The website reads the shared data; the scheduled Worker updates it.
03 / THE FAST PATH
Imports prepare a shared dashboard snapshot, including trends and alert history. Public data responses can be reused for 25 seconds. Snapshots older than ten minutes fall back to the source rows; neither step changes the observation time.
04 / THE PAGE ASSETS
Styles, scripts, logos and illustrations are served as static files. Fingerprinted build assets use long-lived caching; dynamic pages and browser data responses use no-store so a return visit checks for fresh information.
05 / THE SUPPORTING PIECES
Workers KV supplies Astro’s session binding; the environmental readings live in D1. Cloudflare connects the website to gowerlive.co.uk and redirects HTTP and www to the HTTPS root domain.
06 / KEEPING TRACK
Each import records its outcome in the database, and Worker observability is enabled. D1 Time Travel provides database recovery history. Automated external alerts and offsite backups are still planned.
Ozolio streams and WeatherLink’s embedded dashboards load directly from their providers. They do not pass through our Workers or the shared data cache.