Pixelairport's avatar

How to start every Project (Boilerplate, Laravel or Components)

Hi. I try to make it short. Everytime I start a new project I think about this .... What is your way to start new projects. I mean what makes most sense, when you use 90% the same packages, tools, ... ? Do you have a laravel in your own repo, which you will setup and update from original source and then clone your project from there instead the original laravel? Or do you write composer packages and use the service providers in your packages to register everything, or do you use a fresh laravel everytime you make a new project, because some things will be different? I talk about thinks like user authentication, emai templates, tailwind, ... I have to setup a lot things everytime I start a new project. Also for nova I would prefer to have some things out of the box like setup user permissions for each user.

ps: I know some people prefer one over another, but maybe you can tell me why it is good to make it one way instead the other.

0 likes
1 reply
Braunson's avatar
Braunson
Best Answer
Level 18

Both. I have a boilerplate/skeleton but depending on the project I may start fresh a la laravel new. Really depends on your needs. If you are requiring 90% of the same packages/tools, create a boilerplate repository to fork/copy and use to build off your projects.

There's no right way, the right way is what works best for you 😊

1 like

Please or to participate in this conversation.