Quickstart
This is the shortest possible path from cloning the repo to opening a public link in a browser.
Prerequisites
You will need a recent Node.js, pnpm, and a Cloudflare account (for the managed runtime). Nothing else is required for the local walk-through below.
Local install
git clone https://example.com/vegastack.git
cd vegastack
pnpm install
pnpm devThat's it. pnpm dev runs a predev bootstrap that:
- Creates
apps/web/.env.localfromapps/web/.env.exampleif it's missing. - Applies any pending DB migrations to the local Postgres database.
- Seeds a default admin (
dev@vegastack.local) + a "VegaStack" workspace + a "My Space" space if none exists.
The dev server listens on http://127.0.0.1:3000.
Signing in
Sign-in is self-service via Better Auth — email + password, magic link, email OTP, or Google. There is no setup form and no setup token.
The dev bootstrap seeds a default admin (dev@vegastack.local) with the password from VEGASTACK_DEV_ADMIN_PASSWORD (default dev-admin-password-12!); sign in with those on /login. By default (no email env needed), magic-link and OTP emails are printed to the dev server log so you can complete passwordless or signup flows locally without an inbox; setting the VEGASTACK_AWS_SES_* credentials in .env.local switches dev to real delivery via AWS SES.
Keeping up to date
Pull the latest from main and run pnpm dev again — the predev hook re-runs migrations against your dev DB before next dev starts. Your existing pages, comments, and settings survive every migration we ship (we treat the dev DB the same as production data: additive ALTERs, copy-and-rename for any restructure).
If you ever want to start over: pnpm db:reset wipes apps/web/.vegastack/ and re-bootstraps.
Without starting the server
pnpm db:migrate # apply pending migrations only (no server)
pnpm db:reset # wipe local data + re-bootstrap
pnpm preview # build with OpenNext + serve under wrangler (prod-parity)Write your first page
Click New in the sidebar, choose New page, give it a title, and save. The editor saves source on every change and snapshots a version on demand.
Share a public link
Open the page actions menu and choose Share. Turn on the Anyone with the link public link and set it to View or Comment, optionally add an expiry or password, then copy the public URL. The page is served live — rendered server-side and cached by content hash for fast public reads, refreshing automatically whenever you save.
Next steps
- Read Getting started for the longer narrative.
- Read Concepts for the model behind pages, folders, access grants, and review events.
- Read Self-hosting to deploy.