This is a starter laravel 11 project that utilize Tabler admin template by Paweł Kuna.
This project is still a work-in-progress (read to-do below).
- Git
- PHP >= 8.2
- Composer
- Databases (MySQL/MariaDB or PostgreSQL)
-
Clone repostiory
git clone https://github.com/gemul/laravel-tabler-starter -
Install composer dependencies
cd laravel-tabler-starter composer install -
Configure the
.envfile -
Run the migration and seeding
php artisan migrate --seed -
Link the storage to public folder (for user avatar)
php artisan storage:link -
Run the project
php artisan serve -
Access
http://localhost:8000in web browserthe default login is username
developerand passwordpassword
I’ve set up the Tabler template and divided it into different parts such as the main layout, navigation section, and main content area, so there’s no need for you to do it.
In this starter kit, user authentication features are already set up, including registration, login, logout, password reset, password change, user avatars, and email verification.
For this starter project, it’s it is advised (not enforced) to use ULID as the main identifier. One of the reason is to help ensure that the client-side apps work well with the API in the future because it doesn't rely on incremental integer, so that the client side app can safely generate an ID without any conflict with server-generated ID. And unlike UUID, ULID still maintain orders of creation thus make it sortable. I've already set up the basic tables in the migrations to use ulid. See ULID.
We recommend using XHR/Ajax instead of regular HTTP form submission. This allows for better control of requests, such as displaying loading animations or handling server responses like showing errors or validation messages. We've provided an example for the login page using vanilla JavaScript XHR, but you can also use XHR libraries like jQuery or axios if you prefer.
The Laravel framework is open-sourced software licensed under the MIT license.
Tabler is licensed under The MIT license. Which means that you can use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the final products.