Time is money and setting up a project can be time consuming when you could be working on the business logic instead.
Every part of the SvelteKit Enterprise Stack is optimized to go blazingly fast to please stakeholders and uses:
Every part of the stack is modular and easy to replace.
You can configure anything you want from your database to authentication if you read their respective documentation — for example Prisma is configured with SQLite because it requires no setup but it's trivial to change the database connector to use PostgreSQL, MySQL, MongoDB, CockroachDB or Microsoft SQL Server without having to change the Prisma schema.
Stripe payment is set up to give you a starting point how to do Stripe payments with SvelteKit but easy to remove if you don't need payments.
.env
file for local development or the dashboard of your hostproductId
stripe/webhook
where you can add logic to respond to events like checkouts or if an invoice has been paid to continue or revoke access to your productYou can find a Stripe subscription example at /pricing
but you're going to need to understand how to work with the Stripe API to change it to what you want and update your Prisma schema to give users access based on what they purchased.
There's so many things you can do with the Stripe API like using their client library to get a dynamic pricing table if you want but I wanted to keep things simple.
You might want something more custom like Stripe elements in which case you can look at the svelte-stripe package that has a simple integration with instructions and examples.
If you want something simpler let Stripe handle everything and create a payment link for the product you create and just use that link.
You can start a new project by pressing "Use this template" at the top which copies the project with a clean history.
You can use degit
to download the project if you don't want to create a new repository, or if you're not using GitHub which also gives you a clean slate to start from.
pnpx degit joysofcode/enterprise-stack
You can use any package manager of your choice but I recommend you use pnpm because it's fast and doesn't destroy your hard disk because it symlinks packages.
pnpm i
.env.example
to .env
and set your environment variablesIf you're using a host like Vercel you have to enter the environment variables in their dashboard.
# Prisma
DATABASE_URL="file:./dev.db"
# Stripe
PUBLIC_STRIPE_KEY="pk_test_1234"
SECRET_STRIPE_KEY="sk_test_1234"
STRIPE_WEBHOOK_SECRET="we_1234"
pnpx prisma db push
Using db push
is great for prototyping but you might want to use Prisma migrate for production.
You can change the database schema inside prisma/schema.prisma
and run pnpx prisma studio
to look at your database.
pnpm run dev
You can use any SvelteKit adapter that deploys to a target that supports a Node.js runtime.
If you don't have a full-stack hosting solution you can provision a serverless PostgreSQL database provider using Railway or Supabase and host your frontend on Vercel starting at no cost.
pnpm run build
You can also preview the build.
pnpm run preview