Laravel Basic Boilerplate To Kick-Start Any Back-end System

[saurabhnaruka91]

For Laravel Basic boilerplate should have the following things already working and installed:

1. Obviously Laravel LTS itself.
2. Auth and login functionality to admin panel.
3. Middleware or Gates setup for RBAC.
4. xss Middlleware should be registered to filter all the requests.
5. Some basic services to get user information to the controllers.
6. For kick start AdminLite theme should be installed.
7. FOR Encryption and Decryption using AES 256 a trait or a helper should be loaded in bootstrap.
8. Google captcha which can be turned on and off using .env
9. Basic Password validation trait for validating => min 8 char, at least 1 numeric, 1 special, 1 upper case and so .

So this can be a basic boilerplate to kick start laravel admin panel. By this, we can save at least 3-4 days of effort maybe more for a developer.

And this thing can also help us in client interviews whenever the client gives any test. at-least our candidate will not waste their time in setting up this and can focus on the main functionality.

Please provide your inputs

[maulikbhojani]

Even more we can think of boilerplate for Just APIs (as now a days frontend frameworks are more in use - so just APIs in Laravel).

• RBAC
• Auth
• User Management
• Throttling
• Security
• Repository Pattern
• Jobs and Queue configuration
• Environment configurations
• Localisation
• API Versioning (we can standardise this)

Please comment!

[Gurpreetbains]

• Use only BLADE ENGINE for views.
• Minimum use of DB query instead use ORM Eloquent
• Prepare seeder and migrations for admin login and other common tables

[M0hdShabbir]

• Multiple authentications in API using Scope
• Create module separate Application, Register directory (views, controller, and so on) in service providers
• Multi DB Connection with Models & DB queries
• Exception Handling
• Create SPA (Inertia and Livewire or JetStream)
• Manage Logs on a daily basis
• Prepare Model factories for dummy records
• Application Testing (tests folder)
• Route Grouping

[tanurajS]

• For maintaining coding standards we can use some packages like -eslint
• A horizontal implementation for the services. Which is capable to adapt all types of dynamic HTTP request
• Single command for setting up new module. On hit of single command model, controller, crud file view structure should create

[sujit3472]

• For server-side validation need to use request files
• File upload uses the common helper function & resizes images if required
• Use of constant file for common variables
• CMS module to directly create the pages from the backend (e.g. About us, privacy policy pages, etc) with slug generator

[santoshshinde2012]

Do we have any reference url ?

@vinay-patil-neosoft @maulikbhojani

[vinay-patil-neosoft]

@santoshshinde2012 https://laravel-boilerplate.com/ this is one boilerplate reference, we can start with

[saurabhnaruka91]

Agreed @vinay-patil-neosoft ,
And we can add a few other modules to it as suggested above by the team.