create-alopex
v0.4.0
Published
One command to self-host Alopex: Supabase backend, scheduled bank sync and the dashboard on Vercel.
Readme
create-alopex
One command to self-host Alopex:
npx create-alopex # installs into ./alopex
npx create-alopex ~/money # or a folder you choose
npx create-alopex --help # usage and optionsNeeds Node 20+. No git, Docker, Homebrew or GitHub account: the Supabase and Vercel CLIs run through npx.
| Step | Automatic? | | --- | --- | | Download backend + dashboard | yes | | Supabase sign-in | opens your browser | | Project, tables, Edge Functions, secrets | yes | | Your login, public sign-ups off | you type email + password | | Enable Banking app (PSD2) | manual, about 10 min on their site: no API exists for it | | Gemini key | optional, you paste it | | Scheduled sync (pg_cron in Supabase, every 6 h) | yes | | Dashboard on Vercel | opens your browser to sign in, then yes |
To update, run npx create-alopex@latest from the same place as the first time, or inside the
install folder (@latest so npx doesn't reuse an older cached installer). It re-downloads the
code, keeps backend/.env, applies new migrations and functions, and redeploys the dashboard.
Each installer version downloads the release tag v<version> of both repos and runs exact
Supabase / Vercel CLI versions, so nothing changes under you between releases.
Release: tag v<version> on both repos, then npm publish from installer/.
Forks and testing: ALOPEX_BACKEND_REPO, ALOPEX_DASHBOARD_REPO (owner/name) and
ALOPEX_REF (tag or branch; ALOPEX_REF=main to try unreleased code) choose what is downloaded.
ALOPEX_BACKEND_DIR / ALOPEX_DASHBOARD_DIR copy a local checkout instead (try changes before pushing).
Tests: node --test installer/*.test.js (from the backend repo root; a bare installer/ would also run the installer itself).
