Updates

Your purchase includes lifetime access with weekly updates. It is a one-time payment, not a subscription.

How updates are delivered

Weekly updates → your kit repository (main) → your upstream/main → merge into your project

• Every update is pushed to your kit repository (saas-laravel-starter-kit-vue, -react or -svelte).
• Updates are published weekly. Your kit repository's main branch always has the latest version.
• See what changed in each update on the Release Notes page.
• To get notified, watch the repository on GitHub (Watch → Custom → Releases/All activity).

Recommended remote setup

Keep the kit as upstream and your own repository as origin:

Important

Keep your copy of the kit in a private repository. If you push it to a public repository, anyone can see the full source code of the paid starter kit — and publishing it is not allowed under the SaaS Laravel Commercial License.

Choose Private when you create the repository. Already created it as public? Open the repository's Settings → General → Danger Zone → Change visibility and switch it to private.

Private

PublicAnyone on the internet can see this repository.

PrivateYou choose who can see and commit to this repository.

Remote	Points to
origin	Your project, e.g. git@github.com:your-org/my-saas.git
upstream	The kit, e.g. https://github.com/erag-labs/saas-laravel-starter-kit-vue.git

Cloned the kit directly

git remote rename origin upstream
git remote add origin git@github.com:your-org/my-saas.git
git push -u origin main

Started from a copy

git remote add upstream https://github.com/erag-labs/saas-laravel-starter-kit-vue.git
git fetch upstream
git merge upstream/main --allow-unrelated-histories

Check the result with git remote -v. With the All Starter Kits bundle, add each kit you use as the upstream of the project based on it.

Pulling an update

1. Merge the kit on a separate branch:

   git checkout -b kit-update
   git fetch upstream
   git log --oneline HEAD..upstream/main    # what changed
   git merge upstream/main

2. Resolve conflicts, then bring dependencies, databases and generated files up to date (commands below).

3. Merge kit-update into your main branch when everything passes.

Commands to run after merging

composer install
npm install
php artisan migrate
php artisan tenants:migrate
php artisan erag:generate-lang
php artisan typescript:transform
php artisan wayfinder:generate --with-form
npm run build
php artisan test --compact

Check new migrations

Read new files in database/migrations and database/migrations/tenant before running them in production, and back up your databases first. Seeders may also change (menus, permissions); re-run them where needed (see Users, roles & permissions).

Fewer conflicts

• Add new features as new modules in Modules/ and new pages/components instead of editing kit files in place.
• Keep your translations in new files under lang/<locale>/modules/.
• Add new permissions in new files in config/permissions/.
• Generated files (resources/js/lang, resources/js/types) conflict often. Take either side, then re-run the generators above.

Cherry-picking

To take a single fix only:

git fetch upstream
git log --oneline upstream/main
git cherry-pick <commit-sha>