Files
rose-ash/blog
giles 95bd32bd71
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 6m2s
Decouple cross-domain DB queries for per-app database split
Move Ghost membership sync from blog to account service so blog no
longer queries account tables (users, ghost_labels, etc.). Account
runs membership sync at startup and exposes HTTP action/data endpoints
for webhook-triggered syncs and user lookups.

Key changes:
- account/services/ghost_membership.py: all membership sync functions
- account/bp/actions + data: ghost-sync-member, user-by-email, newsletters
- blog ghost_sync.py: stripped to content-only (posts, authors, tags)
- blog webhook member: delegates to account via call_action()
- try_publish: opens federation session when DBs differ
- oauth.py callback: uses get_account_session() for OAuthCode
- page_configs moved from db_events to db_blog in split script

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-25 11:32:14 +00:00
..
2026-02-24 20:13:00 +00:00

Blog App (Coop)

Content management, Ghost CMS sync, navigation, and the prose editor for the Rose Ash cooperative platform. Runs database migrations on startup and serves as the primary content hub.

Structure

app.py                  # Application factory (create_base_app + blueprints)
path_setup.py           # Adds project root + app dir to sys.path
entrypoint.sh           # Container entrypoint (migrations, Redis flush, start)
bp/
  blog/                 #   Post listing, Ghost CMS sync, webhooks
  post/                 #   Single post view and admin
  admin/                #   Settings admin interface
  menu_items/           #   Navigation menu management
  snippets/             #   Reusable content snippets
  fragments/            #   nav-tree fragment for cross-app navigation
models/                 # Re-export stubs pointing to shared/models/
services/               # register_domain_services() — wires blog + calendar + market + cart
templates/              # Blog-specific templates (override shared/)

Cross-domain communication

All inter-app communication uses typed service contracts (no HTTP APIs):

  • services.calendar.* — calendar/entry queries via CalendarService protocol
  • services.market.* — marketplace queries via MarketService protocol
  • services.cart.* — cart summary via CartService protocol
  • services.federation.* — AP publishing via FederationService protocol

Fragments served

  • nav-tree — site navigation tree, fetched by all other apps

Fragments consumed

  • cart-mini (from cart) — cart icon + badge
  • auth-menu (from account) — sign-in / user menu
  • container-nav (from events, market) — sidebar widgets
  • container-cards (from events) — event cards on listing pages