You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2FJCFcodex%2FAinzStack&env=NEXT_PUBLIC_APP_URL,NEXT_PUBLIC_SUPABASE_URL,NEXT_PUBLIC_SUPABASE_ANON_KEY,SUPABASE_SERVICE_ROLE_KEY,NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY,STRIPE_SECRET_KEY,STRIPE_WEBHOOK_SECRET,SANITY_PROJECT_ID,SANITY_DATASET,RESEND_API_KEY&project-name=ainzstack&repository-name=ainzstack"><imgsrc="https://vercel.com/button"alt="Deploy with Vercel"height="32" /></a>
14
+
15
+
<ahref="https://render.com/deploy?repo=https://github.com/JCFcodex/AinzStack"><imgsrc="https://render.com/images/deploy-to-render-button.svg"alt="Deploy to Render"height="32" /></a>
AinzStack provides the foundational momentum required to ship robust software. By abstracting away the boilerplate integration of core SaaS primitives, it allows engineering teams to focus immediately on product logic.
49
+
---
27
50
28
-
Auth flows are integrated via Supabase. Billing is wired through Stripe. Marketing and dashboard layouts are production-scaffolded. Sanity and Resend form the content and communication layers. CI/CD, typing, and testing are structurally enforced.
51
+
## Overview
29
52
30
-
### Interface
53
+
AinzStack is a full-stack SaaS starter kit that handles the repetitive integration work so you can focus on building product. Authentication, billing, content management, transactional email, marketing pages, and a dashboard — all pre-wired and production-scaffolded.
|`pnpm build`| Compile the application for production |
150
-
|`pnpm start`| Run the compiled production server |
151
-
|`pnpm lint`| Execute static code analysis via ESLint |
152
-
|`pnpm typecheck`| Validate TypeScript typings |
153
-
|`pnpm test`| Run unit testing suite via Vitest |
154
-
|`pnpm test:e2e`| Run end-to-end testing via Playwright |
155
-
|`pnpm ci`| Run full CI workflow (Lint, Typecheck, Test, Build) |
193
+
The fastest path to production. Click the button to clone the repo into your Vercel account, fill in your environment variables, and deploy — all in one step.
156
194
157
-
---
195
+
<palign="center">
196
+
<ahref="https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2FJCFcodex%2FAinzStack&env=NEXT_PUBLIC_APP_URL,NEXT_PUBLIC_SUPABASE_URL,NEXT_PUBLIC_SUPABASE_ANON_KEY,SUPABASE_SERVICE_ROLE_KEY,NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY,STRIPE_SECRET_KEY,STRIPE_WEBHOOK_SECRET,SANITY_PROJECT_ID,SANITY_DATASET,RESEND_API_KEY&project-name=ainzstack&repository-name=ainzstack"><imgsrc="https://vercel.com/button"alt="Deploy with Vercel"height="32" /></a>
197
+
</p>
198
+
199
+
Vercel will prompt you to provide each required environment variable during setup. Refer to the [Environment Variables](#environment-variables) table for descriptions.
158
200
159
-
## Contributing
201
+
### Deploy to Render
202
+
203
+
Prefer Render? Click the button below to create a new web service from this repository. Render will use the `render.yaml` blueprint in the repo to configure the service automatically.
204
+
205
+
<palign="center">
206
+
<ahref="https://render.com/deploy?repo=https://github.com/JCFcodex/AinzStack"><imgsrc="https://render.com/images/deploy-to-render-button.svg"alt="Deploy to Render"height="32" /></a>
207
+
</p>
160
208
161
-
We value engineering rigor and clear communication. To contribute:
209
+
> **Render setup notes:**
210
+
> - Add all required [environment variables](#environment-variables) in the Render dashboard under **Environment**.
211
+
> - Set the **Build Command** to `pnpm build` and the **Start Command** to `pnpm start` (these are pre-configured in `render.yaml` if the blueprint file is present).
212
+
> - Ensure the Node.js version is set to `22` or higher in your service settings.
162
213
163
-
1. Fork the repository.
164
-
2. Checkout a scoped feature branch (`git checkout -b feature/module-name`).
165
-
3. Commit your changes with descriptive messages.
166
-
4. Execute the validation suite locally (`pnpm ci`).
167
-
5. Open a Pull Request detailing your modifications.
214
+
### Post-Deployment Checklist
215
+
216
+
Regardless of your hosting provider, verify the following after your first deploy:
217
+
218
+
1.**Base URL** — Set `NEXT_PUBLIC_APP_URL` to your production domain (e.g., `https://yourdomain.com`).
219
+
2.**Auth Callbacks** — Register your production callback URI in the [Supabase Dashboard](https://supabase.com/dashboard) under **Authentication → URL Configuration**:
220
+
```
221
+
https://yourdomain.com/auth/callback
222
+
```
223
+
3.**Stripe Webhooks** — Update your [Stripe webhook endpoints](https://dashboard.stripe.com/webhooks) to point to your production URL:
224
+
```
225
+
https://yourdomain.com/api/stripe/webhook
226
+
```
227
+
228
+
---
229
+
230
+
## License
231
+
232
+
This project is licensed under the [MIT License](LICENSE).
0 commit comments