* fix(core): install prisma globally in docker to prevent offline network failures [Patch]
* fix(core): allow universal CORS access in marketplace [Patch]
- allow any origin in marketplace bridge to ensure universal connectivity [Patch]
- remove dead origin filter code [Patch]
- bump version to 1.20.5 [Patch]
`PluginManager.registerPlugin` builds `ctx.env` for each plugin by iterating
`Object.entries(process.env)` and copying entries whose keys start with
`NEXT_PUBLIC_WWV_PLUGIN_`. In the browser bundle this loop comes back
empty even when those vars are set at build time, because Next.js only
inlines `process.env.NEXT_PUBLIC_*` at *static reference sites* — and
`Object.entries(process.env)` isn't a static reference. The result: any
plugin reading `ctx.env.SOMETHING` to override a default URL silently
gets `undefined` and falls back to its hardcoded cloud URL.
Concrete impact: setting `NEXT_PUBLIC_WWV_PLUGIN_DATA_ENGINE_URL` to a
self-hosted data-engine URL has no effect on the marketplace plugins that
read `ctx.env.DATA_ENGINE_URL` (e.g. `wwv-plugin-aviation`) — they keep
calling `https://dataengine.worldwideview.dev/data/...` even when the
operator has explicitly redirected away from it.
Add explicit static references so the values land in `envVars`. Done as
a small allow-list (currently just `DATA_ENGINE_URL`) so adding new keys
is one line.
Also declare `ARG NEXT_PUBLIC_WWV_PLUGIN_DATA_ENGINE_URL` in the
Dockerfile next to the existing public-arg block. Without it, the build
arg passed in via compose isn't visible to Next.js at build time, so
Webpack inlines `undefined` even when the operator sets the env var.
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
The hosted Umami beacon at analytics.worldwideview.dev/script.js is
loaded unconditionally from src/app/layout.tsx, so every self-hosted
instance (anyone running this from GitHub) phones page-view and event
data home to the maintainer's analytics server. There is no env var,
no docs note, and no opt-out — operators discover the call only by
inspecting their browser's network tab.
Self-hosting is the default audience for an open-source project
distributed on GitHub. Defaulting telemetry on for that audience
silently routes their usage data to a third party they didn't choose
to send it to. Privacy posture aside, it's a surprise.
Gate the Umami script tag behind NEXT_PUBLIC_WWV_ANALYTICS === "true".
Default off — the maintainer's own hosted deployment can flip it on
explicitly via build env, status quo for that environment. Self-hosters
get no analytics by default and can opt in if they choose to.
This does not remove the integration, change Umami's website-id, or
alter the CSP allow-list. It only makes the script-tag conditional.
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
Self-hosters who skip Cesium Ion token setup get a globe that boots fine,
then 401s on world terrain and base imagery from `api.cesium.com`. The
cause is invisible — Cesium ships a default Ion token inside its npm
package that they periodically revoke when usage spikes — and most users
don't realize the build inlined an empty `NEXT_PUBLIC_CESIUM_ION_TOKEN`
until they're staring at network logs.
Add a `prebuild` step that prints an actionable warning (token name,
why it matters, where to get a free one) when the var is missing, so
the gap is surfaced when it can still be fixed cheaply. Non-fatal —
build continues — because demo and existing setups may legitimately
rely on the bundled default until it stops working for them.
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
When self-hosted behind a reverse proxy that terminates TLS (e.g. Caddy,
Nginx, Traefik), Auth.js sets the session cookie with the `__Secure-`
prefix because the public URL is https. The middleware's `getToken()` call,
however, sees a plain-http request internally and its auto-detection looks
for the unprefixed cookie name — which never exists — so authenticated
users are infinite-looped back to /login.
Detect the public scheme via X-Forwarded-Proto, AUTH_URL/NEXTAUTH_URL, or
the request URL's own protocol, and pass `secureCookie` explicitly to
getToken().
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
Most state DOTs (NCDOT, WSDOT, GDOT, fallback HLS-failure paths from
Caltrans/511NY) serve traffic cameras as JPEG snapshots that update
server-side every 5–30 seconds rather than as continuous video streams.
The current `<img src={resolvedUrl}>` in `CameraStream.tsx` renders the
URL once and the browser caches the result — so the camera "loads" then
freezes on the first frame, which reads as broken even when the source
is fine.
Add a cache-busted refresh tick that increments every 10s while the
stream is playing and an image source is active. Skipped for HLS, iframe,
and known video platforms (they manage their own playback). Interval is
cleared when the stream stops, so no leaks on tab switch / pop-out.
The bumped query param is namespaced (`_t=`) and appended with the
correct separator depending on whether the source URL already has query
params (NCDOT's `?filename=...` pattern in particular).
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
Co-authored-by: Silvertakana <[email protected]>
The five existing camera fetchers (Caltrans, GDOT, TfL — and 511NY +
WSDOT, here introduced as adapters) follow the same shape — fetch from
upstream, normalize, return GeoJSON features — but each one is wired up
by hand: a fetcher file, often a route file, plus an entry in
`traffic/route.ts`'s `Promise.allSettled` block. Adding a new source
required surgery in three places, the shared type was named after the
first adapter (`GdotCameraFeature`), and the aggregator was take-it-or-
leave-it (no way to ask for a subset).
This PR introduces a small adapter pattern:
- `adapters/types.ts` defines `CameraFeature` (replacing the old
`GdotCameraFeature` alias) and a `CameraAdapter` interface.
- `adapters/registry.ts` collects all adapters, manages per-adapter
caching with overridable TTL, exposes `getAdapterMetadata()` for
client-side discovery, and provides `fetchManyAdapters(ids)` for
selective merging.
- `adapters/{caltrans,gdot,tfl,ny511,wsdot}.ts` are thin wrappers
around the existing fetcher functions. The GDOT adapter additionally
filters out URLs from the retired `navigator-c2c.dot.ga.gov` and
`vss5live.dot.ga.gov` hosts so clients don't ERR_NAME_NOT_RESOLVED
on click.
- 511NY (`/data/getcameras`, ~1,500 enabled cams w/ HLS) and WSDOT
(`/HighwayCameras/.../GetCamerasAsJson`, ~1,600 cams + ~70 ODOT
border crossings) are introduced here. WSDOT requires a key
(`WSDOT_API_KEY`); the adapter declares this so the client can
surface a "needs key, sign up here" hint.
- `traffic/route.ts` reads from the registry and accepts `?sources=`
(comma-separated ids, "all", or "none"). Default behavior with no
query is unchanged — all adapters merge — so existing clients
continue working without modification.
- New `list/route.ts` returns adapter metadata for client-side source
pickers (settings UIs that render dynamic checkboxes per source,
including health/key-required state).
- Old `gdot/route.ts` removed (subsumed by the registry); the matching
`gdotFetcher.ts` is retained so adapters can `import` from it.
After this lands, adding a new state's DOT to the system is one new
file in `adapters/` plus one line in `registry.ts`. No more
`traffic/route.ts` edits, no merge conflicts when two source PRs are
in flight, no plugin updates required (clients pick up new sources via
`/list`).
Supersedes the standalone 511NY (#58) and WSDOT (#59) PRs, which I've
closed; their fetchers and adapters land here as part of the cohesive
restructure.
Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
- Bump version to 2.1.6
- fix: update setup scripts to pull latest image before starting
- fix: set pull_policy to always in self-host compose file
- fix: auto-detect compose container for legacy migration script in setup UI
* feat(cloud): implement Postgres DB adapter, fix static build crashes, and containerize NextAuth/Stripe integrations
* test(marketplace): fix mocks and assertions for multi-tenant Postgres architecture
* feat: rsa jwt license key verification and state integration
* feat: add internal workspace validation route for Edge Functions
* refactor: clean up hub routes and finalize db proxy/adapter for multi-tenant cloud deploy
* feat(cloud): finalize multi-tenant Prisma extensions and workspace routing
* fix(db): correct Prisma 7 better-sqlite3 adapter initialization [Patch]
- update better-sqlite3 adapter instantiation to use configuration object ({ url }) required by Prisma 7 instead of raw Database instance [Patch]
- fix PrismaClientConstructorValidationError by generating client with adapter support [Patch]
* fix(auth): support dynamic origins for local proxies and multi-tenant subdomains [Patch]
- prioritize forwarded headers and request host over hardcoded envOrigin in getRequestOrigin to support subdomain routing [Patch]
- allow ALLOWED_DEV_ORIGIN in marketplace install redirect checks to fix local network development login flows [Patch]
* fix(marketplace): enable dynamic CORS reflection for marketplace API [Patch]
- remove explicit origin array, replacing with origin header reflection to allow marketplace hosted on any domain or local IP [Patch]
- remove global wildcard CORS headers from next.config.ts to harden security against broader app injection [Patch]
* feat(db): create initial postgresql migration
* refactor(db): update remaining files for postgresql
* feat(db): unify database adapter to PostgreSQL-only [Minor]
- replace SQLite adapter with PostgreSQL PrismaPg [Minor]
- remove better-sqlite3 dependencies [Patch]
- finalize docs and implementation plan [Patch]
* fix: resolve prisma client generation and script execution issues with tsx and type module
* feat(db): port tenant isolation logic to new PostgreSQL adapter
* docs: add rule for transparent and narrated agent actions
* BREAKING CHANGE(core): migrate to PostgreSQL and add auto-migration pipeline [Major]
- unified database adapter to exclusively use PostgreSQL [Major]
- implement auto-migration pipeline to pipe legacy SQLite data to Postgres [Major]
- add sqlite to runner stage to support extraction pipeline [Patch]
* feat(core): migrate to Prisma 7 and unify PostgreSQL architecture [Minor]
- removed legacy Prisma SQLite driver and all Better-Sqlite dependencies [Minor]
- updated schema to utilize purely postgresql providers [Patch]
- modified migration scripts to seamlessly convert local sqlite DBs to PostgreSQL containers using keinos/sqlite3 [Minor]
- updated deployment scripts, Coolify pipelines, and Nginx proxy support [Patch]
- injected Prisma Client Extensions for multi-tenant Row Level Security isolation [Minor]
- stabilized PrismaClient initialization utilizing the official adapter-pg runtime pattern [Patch]
- bumped version to 2.1.0
* fix(core): resolve TypeScript compilation errors for CI [Patch]
- fixed NextResponse.json() 3-arg calls to use 2-arg ResponseInit form [Patch]
- replaced invalid 'developer' TrustTier with 'unverified' in parseWwvManifest and load-unpacked route [Patch]
- removed non-existent pluginManager.hotReload() call in DevModeSubscriber, replaced with disable/reload cycle [Patch]
- updated Stripe API version from '2024-04-10' to '2026-04-22.dahlia' to match installed SDK [Patch]
- excluded local-scripts/ from tsconfig to prevent debug scripts from breaking CI [Patch]
* fix(ci): resolve pnpm version conflict in GitHub Actions [Patch]
- removed explicit version: 9 from pnpm/action-setup@v4 — v4 auto-reads packageManager from package.json [Patch]
- updated build job DATABASE_URL from SQLite to PostgreSQL format [Patch]
* fix(docker): add explicit Prisma generator output path for Docker builds [Patch]
- Prisma 7 changed default output location, causing COPY --from=builder to fail
- added output = '../src/generated/prisma' to generator block for consistency
* fix(prisma): update client import path and resolve CI type errors [Patch]
- updated PrismaClient import in db.ts to point to custom generated output path
- resolved implicit 'any' error in marketplace check-updates route
- verified clean local build with tsc --noEmit
* chore(deps): sync Prisma versions to 7.6.0 [Patch]
* feat: implement local docker HTTPS proxy for marketplace bridge
Generates self-signed certs automatically in docker-entrypoint and spins up a native Node HTTPS proxy on port 3001 to resolve Firefox Mixed Content blocks when fetching from local containers via the live marketplace.
* fix(core): fix docker build and marketplace origin parsing [Patch]
- fix pnpm run generate script failure in Dockerfile [Patch]
- implement robust origin parsing for marketplace endpoints [Patch]
* fix: enlarge panel pull tab trigger areas for better touch targets
* fix: extend trigger area further inward towards panels
* fix(globe): increase mobile pinch zoom sensitivity [Patch]
- decrease _zoomFactor to 5 to make pinch zooming more responsive on touch devices [Patch]
- conditionally allow dev origins in next config [Patch]
---------
Co-authored-by: Antigravity AI <[email protected]>
* docs(core): comprehensive documentation overhaul
* fix: resolve worktree paths dynamically via git CLI
* refactor(ui): temporarily disable demo ad strip
* fix(ui): redirect header logo and cleanup marketplace routes [Patch]
- make header logo a clickable link to landing page [Patch]
- cleanup marketplace routes and remove builtinPlugins [Patch]
* fix: silently drop malformed legacy built-in plugins from marketplace API validation to prevent console spam
* feat: add Sentry captureMessage for marketplace manifest validation errors to improve observability
---------
Co-authored-by: Antigravity AI <[email protected]>
* fix: silently drop malformed legacy built-in plugins from marketplace API validation to prevent console spam
* feat: add Sentry captureMessage for marketplace manifest validation errors to improve observability
---------
Co-authored-by: Antigravity AI <[email protected]>
- Added seedDefaultPlugins pipeline for idempotent initial hydration
- Migrated legacy hard-coded plugins from builtinPlugins.ts to defaultPlugins.ts
- Updated /api/marketplace/load to trigger seeding on fresh installs
- Added support for Antigravity worktrees in local test script
- (Minor version bump for new automated seeding feature)
Co-authored-by: Antigravity AI <[email protected]>
- add wwvStaticCompiler to SDK vite/ subpath export [Minor]
- export createPluginContext and PluginContext type from SDK [Minor]
- update viteGlobals mapping for lucide-react [Patch]
- overhaul all docs/ for decoupled plugin development workflow [Minor]
- update README with new CLI-based plugin creation instructions [Minor]
- fix marketplace load route CORS and error handling [Patch]
- add test coverage for DeclarativePlugin edge cases [Patch]
- bump root to v1.18.0, SDK to v1.5.0