Make It Yours

The template ships saying {{APP_NAME}} everywhere on purpose: one search-and-replace makes it yours. This page is the short version of the repo's docs/FORKING.md, in the order that avoids mistakes.

1. Name it

Set the name in .env:

APP_NAME=QRWizard

Then replace the literal {{APP_NAME}} placeholder across the repo (README, emails, page titles). In VS Code: Search → Replace in Files → {{APP_NAME}} → your name. docs/FORKING.md lists the handful of files worth eyeballing after.

Before:

After, with nothing changed but that one value:

2. Brand color

One value drives the UI accent. docs/FORKING.md §2 shows the exact line in the Tailwind palette to change. Rebuild with -Reload and the whole product wears your color.

3. Your plans and pricing

Plans are data, not code. In the admin console under Plans, rename the seeded Free/Pro plans, set monthly credit amounts and rate limits. Stripe price IDs plug in later when you wire payments.

4. Replace the example endpoints

Keep qr_code if you're shipping it; delete the reference examples you don't need (hello, async_demo, summarize_url, generate_image, transcribe_audio): remove each folder under apps/app_endpoints/ and its line in config/settings/base.py. The safe-to-delete list is in docs/FORKING.md §"What's safe to delete on fork".

5. Move to YOUR repo

Right now your remote points at our template (read-only for you). Your product needs its own private repo:

git remote rename origin upstream
git remote add origin https://github.com/YOUR-USER/your-product.git
git push -u origin main

You push your product to origin. When we ship template updates, you pull them from upstream:

git fetch upstream
git merge upstream/main

The repo's UPGRADING.md has the conflict-resolution playbook for when a template update touches a file you changed.

Next: Put It on the Internet.