laravel-boilerplate VS laravel-debugbar

laravel-boilerplate

cd /opt/bitnami/ mkdir projects && cd projects git clone https://github.com/rappasoft/laravel-boilerplate cd laravel-boilerplace cp .env.example .env composer install npm install npm run prod php artisan key generate php artisan storage:link sudo chown -R daemon:daemon /opt/bitnami/projects/laravel-boilerplate/storage sudo chown -R daemon:daemon /opt/bitnami/projects/laravel-boilerplate/bootstrap

So you don't think I did all this because I didn't make it open source? It wasn't meant to be an open source project, I said I built a blog for myself. If you want some open source projects, I · have · a · few.

If you need a rather basic setup boilerplate I can recommend https://github.com/rappasoft/laravel-boilerplate aswell as the standard "Jetstream" which comes in v8. I currently use that + Orchid as a admin panel for any new smaller project.

debugbar And n+1 query

tldr using debugbar is a good point, everything else is just use laravel when using laravel and avoid n+1 problem

Nice but I can get the same functionality with the debugbar - what makes this better?

We then used platform-specific performance analysis tools to determine which of these endpoints needed the most attention. The highest-traffic sites we needed to optimize used Laravel, a popular PHP framework. We used Laravel Debugbar to analyze those web apps.

Try installing laravel-debugbar, it will show you which parts of the app are slow (e.g. boot up vs views), which queries are slow, and how many queries run (helpful when you forgot to eager load some models).

I wanted to tweak Laravel Debugbar, so it could also work with any JSON API, but I ended up writing a minimal package of my own to do the trick.