I built a Laravel SaaS Starter Kit so you don't have to (Auth + Roles + Stripe + Docker)

Nguyen Hoang Long — Wed, 10 Jun 2026 09:01:33 +0000

Every time I start a new Laravel project, I spend the first 2-3 days
doing the exact same thing.

Set up authentication. Build a role system. Wire up Stripe.
Configure Docker. Write the same middleware I wrote last time.

Sound familiar?

So I stopped copy-pasting and built a proper starter kit.

What's inside

Authentication via Laravel Sanctum

Register, login, logout
Token-based API auth
Get current user endpoint

Roles & Permissions

Admin / Manager / User out of the box
Role middleware protecting routes
Assign and revoke roles via API

REST API — versioned and clean

All routes under /api/v1/
Consistent JSON response format


json
{
  "success": true,
  "message": "Registration successful",
  "data": {
    "user": { ... },
    "token": "1|abc123..."
  },
  "errors": null
}

Stripe Integration
- Create customers and payment intents
- Webhook handler for payment_succeeded / payment_failed

Docker & DevOps
- Multi-stage Dockerfile (PHP 8.3 + Nginx)
- docker-compose with MySQL + Redis
- GitHub Actions CI/CD pipeline

Tests — all passing
✅ test_user_can_register
✅ test_user_can_login
✅ test_login_fails_with_wrong_credentials
✅ test_authenticated_user_can_fetch_profile
✅ test_user_can_logout

Quick start

composer install
cp .env.example .env
php artisan key:generate
php artisan migrate --seed --seeder=RoleSeeder
php artisan serve

That's it. Your API is running with auth, roles, and a seeded admin account.

Preview the structure

Full folder structure and API docs on GitHub:
👉 github.com/long260398/laravel-saas-starter

Get the full source code

If this saves you even half a day of setup, it's worth it.

👉 longnguyen77.gumroad.com/l/nhxta — $29

Built with Laravel 11 · PHP 8.3 · 2026

I built two CLI tools that save me time on every project

Nguyen Hoang Long — Wed, 03 Jun 2026 05:25:03 +0000

Every project I start hits the same two friction points:

I stage my changes and stare at the terminal thinking "how do I word this commit?"
I clone a repo, copy .env.example to .env, run the app, and get a cryptic error because three keys are missing from .env.example.

So I spent a weekend building two small tools to fix them permanently.

gitmage — Stop writing commit messages

npm install -g gitmage
git add .
gitmage

It reads your staged diff, sends it to AI (Groq for free, Claude Haiku for ~$0.0001),
and presents 3 commit options you navigate with arrow keys.

Hit enter to commit. Hit R to regenerate. That's it.

Flags worth knowing:

--push — commit and push in one command
--lang=ja — commit message in Japanese (or vi, zh, ko, es...)
--dry-run — preview suggestions without committing
--provider=claude — force Claude even if Groq key is set

→ https://github.com/long260398/gitmage

envpatch — Never deploy with a broken .env again

The workflow I used to do:

cp .env.example .env

manually compare files

hope I didn't miss anything

deploy

production error: "DATABASE_URL is not defined"

The workflow now:

envpatch init # creates .env from .env.example

fill in your values

envpatch check # confirms nothing is missing

And when a teammate adds a new key to .env.example:

envpatch sync # adds the missing keys to your .env automatically

Also works great in CI:

run: npx envpatch check # fail the build if .env is incomplete

→ https://github.com/long260398/envpatch

Both tools are TypeScript, published on npm, MIT licensed.
Would love feedback if you try them.

DEV Community: Nguyen Hoang Long