What do you need to open the app locally?
The current quickstart uses Clerk for sign-in and a PostgreSQL database for records. It lists Stripe, analytics and email as optional for the first local boot. A sign-in screen or an email preview does not mean those extra services are ready to use.
Before running your copy, check which Node.js version it requires. Node.js runs the local development tools and server.
What will you need to connect before charging a customer?
Choose the parts you intend to ship and connect Stripe if you use the included billing integration. Set up what should happen when the billing service sends your app an update, such as when a subscription is cancelled. The code can connect the pieces, while your team defines what each customer can use.
The official template uses the MIT license. Budget separately for the service accounts you actually enable and for the places you host the app and marketing site.
What should you keep after copying the starter?
Keep your project repository, database change history and a private list of which accounts each app part uses. Follow the template’s change history and review relevant updates before applying them to your own copy.
Check the marketing site and the signed-in app separately after a shared change. If the change touches billing, confirm the disposable payment environment before sending any test events.
How can you decide which parts to set up first?
Draw the marketing site and signed-in app for a fictional workshop. Use no keys, sign-ins or provider accounts.
- Connect the first screenMark the sign-in and database services the signed-in app would need.
- Leave optional services blankDraw the first screen with billing and email disabled. Mark what a person should still be able to do.
- Plan the next checkWrite which disposable services you would confirm before testing payment or email. Leave actual boot and delivery untested.