forked from stripe/projects-template-registry
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathexample.yaml
More file actions
72 lines (66 loc) · 2.63 KB
/
Copy pathexample.yaml
File metadata and controls
72 lines (66 loc) · 2.63 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
# Copy this file when creating a new template manifest.
guided:
# Choose which guided category this template appears under in `init guided`.
category: saas
# Pick the framework filter key this template should match in guided mode.
framework: nextjs
# Use one shared template id for all variants of the same starter.
template: stripe/nextjs-saas
# Give this concrete variant its own stable id.
variant: amber-fox
# Set this to `true` for the variant the CLI should recommend first.
default: true
# Write the short stack summary shown in the variant picker.
variant_description: Vercel • Neon • Clerk
# Optionally run one shell command after files are copied into the new project.
install_command: npm install
metadata:
# Show this human-friendly name in browse results and confirmation cards.
name: Next.js SaaS Starter
# Explain in one line what the starter gives the user.
description: Subscription SaaS with auth, database, and billing
# Name the team or person maintaining this template.
owner: stripe
# Add optional search keywords to improve browse and search results.
tags:
- Billing
- SaaS
- Next.js
# Point to the repo directory the CLI should copy from.
repo: https://github.com/stripe/projects-templates/tree/main/nextjs_saas_amber-fox
# Pin the exact commit so users get a reproducible template.
ref: 84315765f28e9ad2d0b3c7167447edf6f65bcebe
# List the provider services the provisioning pipeline should provision.
services:
- vercel/project
- clerk/auth
- neon/postgres
# Optionally list the commands the CLI should print after setup finishes.
next_steps:
# Use a short heading so users know what this command is for.
- label: Run locally
# Print the exact command the user should run next.
command: npm run dev
# Add as many labeled next-step commands as you want.
- label: Build product with Codex
command: codex "Help me turn this into a real product. Follow prompts/starter-to-product.md."
- label: Build product with Claude
command: claude "Help me turn this into a real product. Follow prompts/starter-to-product.md."
- label: Deploy
command: npm run deploy
# Optionally override which provider plan each traffic tier should pick.
tier_plans:
# Use the provisioned service slug as the top-level key.
vercel/project:
# Use a string when the provider expects a named plan id.
free_lowest_cost: Vercel/hobby
starter_paid: Vercel/pro
higher_scale: Vercel/pro
clerk/auth:
free_lowest_cost: Clerk/hobby
starter_paid: Clerk/pro
higher_scale: Clerk/pro
neon/postgres:
free_lowest_cost: Neon/free
starter_paid: Neon/launch
higher_scale: Neon/launch