Download the PHP package n1crack/laravel-starter-kit without Composer
On this page you can find all versions of the php package n1crack/laravel-starter-kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-starter-kit
Laravel Starter Kit
A Laravel kit that asks what you are building and installs only that.
Requirements
PHP 8.4 · Node 22
Getting started
The install asks four things:
Answering yes to multi-tenancy asks two more: which domains serve the application itself, and what tenant database names should be prefixed with.
composer dev runs the server, queue worker, log viewer and Vite together.
To load demo data — an [email protected] account plus 25 users, all with the password password:
What's inside
- Laravel 13, Inertia 3, React 19, Tailwind 4
- Authentication via Fortify: registration, login, password reset, email verification, two-factor
- Roles via spatie/laravel-permission, with an
/adminarea behindrole:admin - Typed routes generated by Wayfinder
- Pest, PHPStan, Pint, Rector, oxlint and Prettier, wired into CI
The admin and user panels are always React. The public-page question only covers the public pages, so nothing in the kit has to exist twice.
Teams
Answering yes adds teams with membership roles (owner, administrator, member),
email invitations, member management, team deletion and a switcher in the
sidebar. Team roles live on the team_user pivot; the application-wide
admin and user roles stay with spatie and are unaffected.
Multi-tenancy
Answering yes installs stancl/tenancy and turns the kit into a tenant-facing application: one database per tenant, resolved from the request domain or subdomain.
Everything the kit ships becomes tenant-owned. Its migrations move under
database/migrations/tenant and its routes move into routes/tenant.php;
the central database is left holding only tenants and domains. There is no
central login — authentication happens on a tenant domain.
Run Composer once afterwards, since the package is only added when asked:
tenants:create makes the tenant, its database, and its first domain, then
migrates it. --seed adds the demo users; leave it off for a real tenant.
The tenant is then served at acme.your-central-domain.
After adding a migration under database/migrations/tenant, apply it to
tenants that already exist:
What is shared and what is not
| Where it lives | Why | |
|---|---|---|
| Users, sessions, roles, teams, your tables | Tenant | Nothing about them is shared |
| Cache | Tenant | Isolated by the connection, not by cache tags — the default database store cannot tag |
| Queue tables | Central | One queue:work serves every tenant; each job is restored to its own tenant |
| Tenants, domains | Central | The registry the request is resolved against |
The cache, session, rate limiter and auth guard are all rebuilt when tenancy
switches. Each is resolved once and then held, so without that a tenant would
read another's rows — and the rate limiter, which guards signing in, would
reach for a cache table the central database does not have.
Tenants themselves are expected to be administered by a separate application.
tenants:create exists so the kit can be run locally.
Layout
| Path | Contents |
|---|---|
routes/web.php |
Public pages and authenticated user settings |
routes/admin.php |
Admin area (auth, verified, role:admin) |
routes/tenant.php |
Tenancy only: wraps the above in tenant identification |
resources/views |
Blade pages and Livewire components |
resources/js/pages |
Inertia React pages |
stubs/ |
The optional features, published by the installer |
Commands
The test suite enforces 100% code coverage and 100% type coverage.
Nothing under stubs/ is covered by those, because the linters only see a
working application. CI therefore installs every combination of answers into a
clean checkout and runs Pint, Rector, PHPStan, type coverage and the test
suite against the result.
License
MIT
All versions of laravel-starter-kit with dependencies
inertiajs/inertia-laravel Version ^3.2.1
laravel/fortify Version ^1.37.3
laravel/framework Version ^13.23
laravel/tinker Version ^3.0.2
laravel/wayfinder Version ^0.1.20
livewire/livewire Version ^4.3
nunomaduro/essentials Version ^1.2.0
spatie/laravel-permission Version ^8.3