emi
92e74c585a
All checks were successful
Sync infra to hosts / sync-beta (push) Successful in 13s
Sync infra to hosts / sync-prod (push) Successful in 12s
secrets-guard / encrypted (push) Successful in 7s
shell-lint / shellcheck (push) Successful in 8s
Build + push frontend image (Forgejo registry) / build-push (push) Successful in 53s
Deploy frontend to beta VPS / deploy (push) Successful in 1m16s
secrets-guard / encrypted (pull_request) Successful in 5s
shell-lint / shellcheck (pull_request) Successful in 6s
Ports frontend/ (Jinja2/FastAPI, ~1180 LOC) to Go with html/template. No climate math, no DB, no auth -- every route fetches from the backend's /content/* API. Verified with a golden-HTML diff, not just unit tests: both the Python original and the Go rewrite were run against the same committed fixtures and every route compared byte-for-byte, confirmed programmatically. That process caught defects unit tests alone missed, since map[string]any has no compile-time field check: - Render-context keys were snake_case throughout while the templates read PascalCase fields. A missing map key doesn't error, it silently renders empty -- title, meta description, canonical URL, OpenGraph tags, and the homepage's entire ranked list were blank on every page despite every route returning 200. Fixed by renaming every key to match each template's own documented field contract, and passing API structs straight through wherever their fields already matched (removes a whole layer of future drift risk). - Three pages 500'd: ToolHref needed a composed href, not a bare "lat,lon" fragment; the records table needed the raw API struct. - JSON-LD was double-encoded: <script type="application/ld+json"> is JAVASCRIPT context to html/template's escaper regardless of the script's type attribute, so template.HTML gets re-escaped as a quoted JS string. Needed template.JS. The glossary term page's JSON-LD was never built at all -- added. - html/template silently strips literal HTML and JS comments from parsed output (verified in isolation) -- both need a FuncMap function returning template.HTML/template.JS to survive. Packaging: 187MB -> 22.6MB. Two defects caught before reaching a host: the Swarm stack's entrypoint override with no explicit command drops the image's CMD entirely (every deploy would have exited 127), and COPY --chown by name fails under the classic Docker builder on Alpine. Both fixed. go build/vet/test -race clean; docker build passes its embedded test step under both BuildKit and the classic builder; shellcheck 0 findings.
30 lines
No EOL
2.2 KiB
Cheetah
30 lines
No EOL
2.2 KiB
Cheetah
{{/* Ported from templates/about.html.j2. Extra data: .Breadcrumb.
|
|
temp(60) renders through the request-scoped formatter (no unit scope on
|
|
this page in Python → °F). */}}{{template "base_head_start" .}}{{template "base_head_end" .}}{{template "base_body_start" .}}{{template "breadcrumb" .}}<article class="climate-page">
|
|
<h1>About Thermograph</h1>
|
|
<p class="lede">Thermograph answers one question for any point on Earth: <b>how unusual is this
|
|
weather?</b> Instead of an absolute temperature, it shows where a day falls in that exact
|
|
location's own climate history.</p>
|
|
|
|
<h2>Where the data comes from</h2>
|
|
<p>The ~45-year daily record (high, low, feels-like, humidity, wind, gust and precipitation)
|
|
comes from the <b>ERA5 reanalysis</b> (ECMWF), served via <a href="https://open-meteo.com/" rel="nofollow">Open-Meteo</a>.
|
|
Because reanalysis is a gridded, model-consistent record, Thermograph works even where there's
|
|
no weather station, anywhere on the ~4 sq mi grid.</p>
|
|
|
|
<h2>How a day is graded</h2>
|
|
<p>For each metric and date, Thermograph builds a reference distribution from every historical day
|
|
within <b>±7 days of that day-of-year</b>, a 15-day seasonal window across all years. The
|
|
observed value is placed on that distribution as an <a href="{{.Base}}/glossary/percentile">empirical
|
|
percentile</a>, then mapped to a grade from “Below Normal” through “High” to “Near Record”.</p>
|
|
<p>Everything is <b>relative to the location</b>: a {{.Fmt.Temp 60.0}} day can be “Above Normal” in one place and
|
|
“Below Normal” in another. Precipitation is graded only among days that actually rained, so “Heavy”
|
|
means heavy for a rainy day <i>here</i>. See the <a href="{{.Base}}/legend">grade guide</a> for the full scale.</p>
|
|
|
|
<h2>Freshness</h2>
|
|
<p>The historical archive updates as new days are added; recent and forecast conditions refresh hourly.
|
|
City climate pages show the latest recorded day graded against the local normal.</p>
|
|
|
|
<p><a class="cta" href="{{.Base}}/">Open the weather grader →</a></p>
|
|
</article>
|
|
{{template "base_body_end" .}}{{template "base_scripts_default" .}}{{template "base_tail" .}} |