agol_fdw Console

What it is

The Console is a frontend web app that drives agol_fdw from the browser instead of SQL. It's built as a GeoLibre plugin host: a small plugin contract ({ id, title, mount, unmount }) and a registry, with two plugins sharing one shell:

• Map Viewer — browse and identify AGOL-backed data on a MapLibre GL map, served as vector tiles straight from the data.* materialized tables.
• Admin console — list layers, run control functions (sync_now, push_outbox, apply_inbound, reconcile_audit), and watch the outbox, inbound queue, conflict log, and sync-run log.

How it talks to the database

The Console holds no SQL. It calls a thin FastAPI layer that wraps the existing agol_fdw.* functions over HTTP — no new business logic. Vector tiles come from an MVT endpoint over the data.* tables, gated by an identifier allow-list and a registered-layer check.

# run the thin API
export DATABASE_URL=postgresql://...
export CONSOLE_API_TOKEN=$(openssl rand -hex 24)
uvicorn app.main:app --port 8000

# run the frontend
npm run dev   # http://localhost:5173

Why it matters

• For DBAs — drive the lifecycle and triage queues/logs without a SQL client.
• For end users — see and explore AGOL-backed data on a map, against the PostGIS source of truth.
• Pluggable by design — add a new plugin module, register it, and it appears in the shell.

Related

← Back to home