Loading repository dataβ¦
Loading repository dataβ¦
reliverse / repository
π¬ relivator: next.js 15 react 19 ecommerce template β² better-auth polar shadcn/ui tailwind drizzle orm typescript ts radix, postgres neon, app router saas commerce ecommerce shop pricing payments dark mode full stack free β more stars π more features
demo β sponsor β discord β github β docs
relivator is a robust ecommerce template built with next.js and other modern technologies. it's designed for developers who want a fast, modern, and scalable foundation without reinventing the backend.
these features define the main reliverse stack. for an alternative setupβfeaturing clerk, stripe, trpc, and moreβcheck out versator.
run:
git clone https://github.com/blefnk/relivator.git
cd relivator
bun install
copy .env.example .env
fill in the required environment variables in the .env file.
optionally, edit the src/app.ts file to make the app yours.
run:
bun db:push # populate db with schema
bun dev # start development server
bun run build # build production version
edit something in the code manually or ask ai to help you.
done. seriously. you're building now.
| command | description |
|---|---|
bun dev | start local development |
bun build | create a production build |
bun latest | install latest deps |
bun ui | add shadcn components |
bun db:push | apply db schema changes |
bun db:auth | update auth-related tables |
bun db:studio | open visual db editor |
relivator now integrates with polar for payment processing and subscription management.
.env:
POLAR_ACCESS_TOKEN="your_access_token"
POLAR_WEBHOOK_SECRET="your_webhook_secret"
POLAR_ENVIRONMENT="production" # or "sandbox" for testing
src/lib/auth.ts to match your polar products:
checkout: {
enabled: true,
products: [
{
productId: "your-product-id", // Replace with actual product ID from Polar Dashboard
slug: "pro" // Custom slug for easy reference in Checkout URL
}
]
}
bun db:push to create the necessary database tablesbun devto verify that the integration is working:
/dashboard/billing)the following api routes are available for payment processing:
/api/payments/customer-state - get the current customer state/api/payments/subscriptions - get user subscriptionsevery bit of support helps keep the dream alive: dev tools that don't suck.
mit Β© 2025 nazar kornienko (blefnk), reliverse