Get Source
Verify access, clone the standalone repository, and preserve your own code and configuration.
This guide starts after purchase and repository access. It establishes the correct Flare checkout; if source is already available, continue with Quick start.
Prerequisites
- Git, Node.js 22.12+ and the pinned pnpm 10.26.2.
- The GitHub account granted access after purchase. MuseMVP and All in One include Flare; UI Templates does not.
- Connect GitHub in Dodo Customer Portal and accept the repository invitation actually issued to you. Documentation cannot grant access; contact support with order/account details if access is missing.
1. Clone the standalone repository
git clone https://github.com/musemvp/musemvp-flare.git
cd musemvp-flare
node --version
pnpm --version
pnpm install --frozen-lockfileFor SSH use [email protected]:musemvp/musemvp-flare.git. Run root workspace scripts from the folder containing pnpm-workspace.yaml and the root package.json, not from apps/web.
There is one TanStack app. The marketing repository musemvp-com is not the SaaS runtime; copying apps/web-cloudflare from the original starter is not part of installation.
2. Record the baseline
git status --short
git log -1 --oneline
git remote -vExpect apps/web, packages, docs, tests and .env.example. Record the baseline commit in your project notes. Source docs/PROVENANCE.md describes origins and AGENTS.md defines ownership boundaries.
These guides and the marketing explorer were checked against Flare b6b68e5. Before adopting future updates, inspect your changes and the upgrade guide.
3. Keep your own private remote
Create an empty private repository in your own account. To keep template access and your project origin separately, confirm the addresses before running:
git remote rename origin template
git remote add origin https://github.com/YOUR_ACCOUNT/YOUR_PRIVATE_REPO.git
git remote -vRun locally and customize before pushing your working branch. Preserve licenses and third-party notices. Do not publish the commercial source as a public template repository.
Files and portability
| File | Purpose | Handling |
|---|---|---|
pnpm-lock.yaml | Reproducible dependencies | Commit; use frozen install |
packages/config/src/index.ts | Product and catalog choices | Commit without credentials |
packages/cli/src/target-resources.ts | Deployment resource names | Commit names chosen for your product |
Root .env | CLI account/deployment settings | Ignored; transfer securely when needed |
apps/web/.dev.vars | Local Worker secrets | Ignored; regenerate with init |
.muse/ and .wrangler/ | Deployment/local state | Ignored; exclude from support bundles |
Verify and troubleshoot
- Installation succeeds without editing the lockfile to bypass an error.
- Remote URLs match your intended template/private repositories.
- Repository not found: check the invited GitHub account, then HTTPS or SSH credentials. Never paste tokens into logs or issues.
- Frozen install fails: check pnpm and the complete lockfile, then network/registry access. Do not delete the lockfile as a first response.
- Local development does not require copying production
.envor sharing a production database.
Continue with initialization and first login.