Vite+ Monorepo Starter

A starter for creating a Vite+ monorepo.

Development

Effect dependencies use commit-pinned CI snapshots. Install with vp install --frozen-lockfile; no local Effect checkout or build is needed. See Effect snapshot dependencies for the pins, compatibility exceptions, and upgrade checks.

• Check everything is ready:

vp run ready

• Run the tests:

vp run -r test

• Build the monorepo:

vp run -r build

• Run everything:

vp run dev

vp run dev runs vp exec alchemy dev directly.

alchemy dev starts both Workers: the API on port 8787, and the web app's own Vite dev server, with hot reload and the foldkit devtools port, on 1337. Open the second one. Deployed, the two Workers share one hostname and Cloudflare routes /api/v1/* to the API; locally that routing is a proxy in apps/web/vite.config.ts.

There is no Cloudflare edge locally, so Access is simulated: every request is attributed to the issuer local-dev, and audit entries written locally say so. A deploy never carries that identity.

Each repository has a separate GitHub sync switch in its Settings section. Turning it off retains cached data and auto-labeling configuration, cancels queued sync claims, and excludes that repository from scheduled repair, manual sync, and sync status totals. Re-enabling requests fresh scans. Work already fetching from GitHub may finish, but its old claim cannot publish results after sync is disabled. Webhook journaling and projection continue to accept events.

Seeded repositories start with sync off while keeping their labeling settings. Their synthetic installation also has sync disabled, so installation inventory does not request a token for fixture installation 77. Real installations and new repositories default to sync on; repository enablement still controls whether Janitor bootstraps their content.

To point the local web app at a deployed stage instead, log in through cloudflared and pass the token along with the origin. Both go in .env, which direnv loads and git ignores:

cloudflared access login https://janitor.effectful.co
cloudflared access token --app https://janitor.effectful.co

JANITOR_API_ORIGIN=https://janitor.effectful.co
CF_ACCESS_TOKEN=<the token>

The token expires with the Access session. Anything you save in that mode changes the deployed configuration.