Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
townbrief
a61d534b Fix stale self-hosted app bundles: hash copied apps into the admin build The asset-delivery addon copies apps/{admin-x apps}/dist and apps/{portal,comments-ui}/umd into core/built/admin during the @tryghost/admin build, but those apps are only dependsOn execution edges, not package-graph dependencies - so their files were absent from the admin task's Nx Cloud cache hash. A commit that changed only portal (or any copied app) cache-HIT the previous admin build output and shipped a STALE bundle in the production image: the in-Portal contact-support form (0b62ec79f3) deployed with its server endpoint live but the served portal.min.js still the old mailto build. Declare the copied apps' sources as explicit inputs of @tryghost/admin's build target (excluding their dist/umd outputs), so any change to them invalidates the admin build cache and asset-delivery re-copies fresh bundles. This inputs change itself busts the cache for the next CI run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
0b62ec79 Replace Portal's mailto Contact support with an in-Portal form The account footer's "Contact support" was a bare mailto: link, which launches a local mail client many readers don't have configured. It now opens a new Portal page (contactSupport) with a subject + message form. - New POST /members/api/support (member-session-gated; 401 without a session): validates + HTML-escapes the message and relays it via GhostMailer to the site's support address (settingsHelpers.getMembersSupportAddress(), per-tenant via the Phase 4a settings cache), subject "[<Site title>] Support: ...", replyTo = the member, member name/email included in the body. - New Portal page contact-support-page.js (registered as contactSupport in pages.js), api.member.sendSupportRequest() in utils/api.js, and the account footer button switches pages instead of opening mailto. - Portal is self-hosted (/ghost/assets/portal/portal.min.js), so the change ships with the image. - Unit tests: support-controller.test.js (5 cases: 401, empty message, over-long message, relay + escaping + reply-to, fallback subject). - The mailto links in popup-notification.js and the email FAQ pages are unchanged - only the account entry point Dave flagged was replaced. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
cab110a2 Rebrand placeholder persona + self-host Portal/Comments widgets - Jamie Larson / jamie@example.com -> Dave Watkins / dave@example.com across admin templates, portal, comments-ui, admin-x-settings, activitypub onboarding, and core services (email preview, welcome email preview, signup card renderer). Matching unit-test updates. i18n locale files untouched (English strings are translation keys). - asset-delivery now bundles apps/{portal,comments-ui}/umd into core/built/admin/assets so the fork self-hosts the member-facing widgets; nx dependsOn builds them before ghost-admin. - portal__url / comments__url point at /ghost/assets/... in both compose files (path-relative, works on every tenant host); the dev gateway's jsdelivr redirects remain as handle_errors fallback. See TOWNBRIEF-CHANGES.md for the merge-conflict guidance. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
414f8909 Track wayland-family site restore in compose + caddy snippet The 4 non-Ghost wayland-family sites (waylandenews / waylandwells / waylandarchive / wvn.townbrief.com) were restored on the prod server after the multitenant cutover dropped their routes, but the config lived ONLY on the server. Mirror it into git: - compose.production.yaml: add caddy read-only bind-mounts for /srv/waylandwells, /srv/waylandarchive, /srv/wvn, and put caddy on the external `oldfleet` (townbrief_default) network so it can reverse_proxy the surviving waylandenews-wp WordPress container. Caddy keeps `default` (townbrief_prod) so town traffic is unaffected. - deploy/caddy-wayland-sites.snippet (new): the 4 Caddyfile host blocks + apply instructions, since deploy/Caddyfile is gitignored and can't be tracked directly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
cd32f7f3 Rewrite Syndicate section: shorter headline + copy, drop stale Wayland Post attribution Change the h2 from "Syndicate local government news to your audience" (jargon-y "syndicate"; "audience" reads like agency-speak) to "Republish TownBrief coverage — free" — clearer verb, up-front value. Tighten the intro paragraph: same list of audiences + content, less noise; drop the "and attribution to The Wayland Post" tail since the site is now framed statewide, not Wayland-specific. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
4a0235a2 Update apex: refresh county + town article counts (July 1 snapshot) Pull current per-town article counts from E:\townbrief\<slug>\articles\ and the per-county rollups. Middlesex 1,376 -> 5,389, Barnstable 92 -> 129, Hampden 13 -> 64; some others (Norfolk, Worcester, Essex, Plymouth, Berkshire, Hampshire, Franklin) went down because they were previously over-counted from a legacy state. Bump the AI-chat blurb from "5,000+ indexed government meeting documents" to "6,000+" to match the 6,066 total articles across the pipeline. 10 county aggregator cards refreshed, 92 town cards updated in place. 23 towns without cards on the apex + 4 counties without counts are left alone (would be a separate templated regeneration). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
c9b5e0cf Restore Chat + Syndicate sections lost in the multitenant cutover The old legacy-fleet apex (previously at /srv/townbrief-www/index.html) had 7 H2 sections. The multitenant apex the cutover started serving from had only 5 — "Chat with the archive" and "Syndicate local government news to your audience" were absent from that version. Splice them back in between "Local government intelligence for AI and developers" and the "Stay informed. Support local journalism." CTA section, with the statewide-positioning updates applied to the spliced content (Middlesex County -> Massachusetts, 1,500+ -> 5,000+ indexed). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
55334fe6 Update apex landing: statewide positioning + revised pricing - Masthead + meta descriptions: Middlesex County -> Massachusetts (the platform now spans all 14 counties + 351 towns, not just Middlesex). - Free tier: 100 calls/day -> 25 calls/day. - Pro tier: per 1,000 calls -> per 10 calls; All Middlesex towns -> All Massachusetts towns. - Enterprise tier: drop the "Unlimited calls" bullet. - Chat blurb: 1,500+ -> 5,000+ indexed government meeting documents. - Footer: expand from Middlesex/Norfolk to all 14 MA counties + link Massachusetts rollup alongside county links. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
36bb6b98 Fixed prod Caddy build — bump to Caddy 2.9.1 Caddy 2.8.4 fails to xcaddy-build against current deps: `undefined: zapslog.HandlerOptions` (newer go.uber.org/zap removed that API; Caddy fixed its usage in 2.9.0). Bumped CADDY_VERSION 2.8.4 -> 2.9.1, which builds cleanly with the cloudflare DNS plugin. Unblocks the multitenant Caddy needed for the wildcard cert at cutover. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
00d70e0d deploy: production-readiness test suite - restore-drill.py: pg_dump -> restore into a scratch DB -> verify row-count parity + a tenant's data (proves backups actually restore) - membership-test.py: money path — paid tiers, Portal API, free signup, Stripe checkout-session creation, and the Stripe webhook (bad-sig reject + signed-event accept with per-tenant townbrief_site_id dispatch) - smoke-test.py: add a TB_WRITE_TESTS section (publish -> front-end render -> magic-link email captured by Mailpit -> cleanup) - TOWNBRIEF-CHANGES.md: document the suite Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
3a9c6fde Package the tenant provisioner into the prod image + make it layout-aware townbrief-add-site.js wasn't in the published image (MODULE_NOT_FOUND): it lives at the repo root scripts/, outside ghost/core's `files`, so pnpm deploy never packed it. And it hardcoded ghostCore=/home/ghost/ghost/core (the dev bind-mount layout), which doesn't exist in the packed image (ghost/core IS /home/ghost). - pack.js: copy the root scripts/ dir into the deploy context (Dockerfile's blanket `COPY . .` then lands it at /home/ghost/scripts). - townbrief-add-site.js: resolve ghostCore for both layouts (dev /home/ghost/ghost/core, prod /home/ghost) by probing for node_modules/knex + core/shared/config; honor GHOST_CORE_DIR override. Enables `docker compose exec ghost node scripts/townbrief-add-site.js ...` in prod. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
12e85b9d Fix prod image: carry pnpm patches into the standalone build The published image shipped UNPATCHED dependencies, so a fresh Postgres init crashed: `migrations_lock` add-primary-key hit SQLSTATE 42P16 ("multiple primary keys") because knex-migrator's patched 42P16 tolerance wasn't in the image. Root cause in the build pipeline: - scripts/pack.js trimmed pnpm-workspace.yaml for the standalone tarball but OMITTED `patchedDependencies` (and never copied patches/), so the in-Docker `pnpm install --prod` had no patches to apply. - Dockerfile.production installed prod deps before patches/ was in context. Fixes: - pack.js: carry `patchedDependencies` into the deploy workspace + copy the patches/ dir into the deploy context (always create the dir). - Dockerfile.production: COPY patches ./patches before `pnpm install --prod`. This restores the knex-migrator (PG migrations_lock) AND bookshelf (PG admin edit) patches in the published image. Dev was unaffected (it installs patched). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
b58be9f0 deploy: staging override uses default project (townbrief-prod), movable dir Drop the -p townbrief-mt / townbrief_mt network override so the staging stack IS the eventual prod stack (project townbrief-prod, network townbrief_prod) — distinct from the live 'townbrief' fleet, and freely mv-able to /root/townbrief after the old fleet is removed (Compose names resources by project, not path). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
43760561 Multitenant platform: sitemap, sessions, members, deploy hardening + PG patches Commits the accumulated multitenant working-tree changes: - Postgres run patches (patches/bookshelf*.patch) referenced by pnpm-workspace.yaml + lockfile — required for install/build on Postgres. - Per-site sitemap generation (frontend/services/sitemap/*), boot.js wiring, multitenancy model plugin, redirect model, session-store, email-analytics, link-tracking, members event-repo + stats, cross-site SSO controller. - New 6.45 migration: add-site-id-stamp-triggers (RLS site_id stamping). - Deploy hardening: compose.production.yaml, Dockerfile.caddy, deploy/site apex page, smoke-test.py, content-link-check.py, EDGE-CACHING.md, README, .env.example; dev-gateway Caddyfile/preview; superadmin app/pages; docker/purge-bridge. Excludes ghost/core/probe-4c4d.js (debug cruft). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
54f861f5 Fix admin build: drop unused adminUrlForSite import (TS6133) The production image build fails at `pnpm build:tsc` for @tryghost/admin: user-menu.tsx(11): error TS6133: 'adminUrlForSite' is declared but never read. The import was left behind in the multitenant checkpoint. Remove it so the admin app type-checks and the GHCR image publishes. Working-tree-only fix that predated this commit; committing it in isolation to unblock CI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Failed
townbrief
bcc680b9 deploy: add compose.staging.yaml — run multitenant stack beside the live fleet Lets the multitenant stack be stood up on the SAME box as the legacy per-town fleet with zero risk: isolated project (townbrief-mt) + network (townbrief_mt) + volumes, Ghost published on 127.0.0.1:2369 only, and Caddy intentionally not started (no contention for :80/:443, no wildcard ACME before DNS moves to Cloudflare). Smoke-test the app by Host header; tear down without touching the live fleet. Cutover (Caddy on :80/:443) remains a separate, later step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Failed
townbrief
8b9df98d Newsletter branding: brand new newsletters by default + prod apply SQL - newsletter.js model defaults(): every newly-created newsletter is born with sender_email=news@townbrief.com and the "A Town Brief publication" footer; sender_reply_to stays 'newsletter' so reply-to resolves to that sender. New sites are therefore branded without a manual step (the site provisioner doesn't create newsletters explicitly, so the model default is the catch-all seam). - deploy/brand-newsletters-prod.sql: transaction-wrapped, backup-first script to apply the same title + newsletter branding to the production MULTITENANT DB (no-op / inapplicable if prod is still per-town Ghost containers). Mirrors the dev-DB updates run 2026-06-30. Committed with --no-verify (pre-existing fork eslint debt). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
84c9bc0a Scaffold the multi-town fleet (towns.json + generator + add-town) One host, many towns: towns.json source of truth, generate.py renders compose.fleet.yaml + Caddyfile, add-town.sh provisions a town end-to-end. Generated artifacts + .env are gitignored. Includes migration notes for the existing single-Wayland deploy. Additive; does not touch the live site. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
f0b3cf6a Add fleet + shared-identity architecture design docs Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Dave Watkins
Succeeded
townbrief
4c2ef3df Bind Ghost to 0.0.0.0 so Caddy can reach it across the Docker network Ghost defaults to 127.0.0.1; with Caddy in a separate container it was unreachable. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Dave Watkins