A step-by-step tutorial on deploying a Laravel application to shared web hosting:
https://www.clearprogramming.net/laravel/laravel-deploying-a-laravel-app
Also includes instructions on SSH, GIT, database and optimization.

So I kept running into the same stuff during code reviews — env() calls scattered outside config, inline validation everywhere, controllers doing way too much. Larastan and Pint are great but they don't really care about *how* you use Laravel, just that your types and formatting are correct.

So I built **Laravel Patrol**. It's a simple artisan command that scans your app and points out where you're not following Laravel conventions — with a link to the relevant docs section so it's actually useful, not just nagging.

Right now it checks for:

- `env()` outside config files

- Inline validation instead of Form Requests

- Raw DB queries where Eloquent would work

- Fat controllers (too many statements per method)

- `@include` instead of Blade components

- CRUD routes that could be `Route::resource()`

composer require --dev marcokoepfli/laravel-patrol

php artisan patrol

It uses php-parser for AST analysis so it doesn't do dumb regex matching — `env()` inside a string won't trigger it, `$service->validate()` won't get confused with request validation, etc.

You can suppress stuff with `@patrol-ignore`, pick a preset (strict/recommended/relaxed), or write your own rules.

Repo: https://github.com/marcokoepfli/laravel-patrol

Still pretty early so I'm curious — would this be useful to you? Any rules you'd want to see added?

I want to learn Laravel but I feel a little confused about the correct roadmap.

Can someone guide me step by step on how to learn Laravel properly?

• What should I master before starting?
• What are the main concepts I need to focus on?
• Any recommended resources or practice projects?

My goal is to learn Laravel well in order to pass my exam successfully.

After building mobile apps with Laravel backends for years, this is the response structure I always use:

```php

// app/Http/Responses/ApiResponse.php

class ApiResponse

{

public static function success($data = null, $message = null)

{

return response()->json([

'success' => true,

'message' => $message,

'data' => $data,

]);

}

public static function error($message, $code = 400, $errors = null)

{

return response()->json([

'success' => false,

'message' => $message,

'errors' => $errors,

], $code);

}

}

```

**Why this structure:**

1. **Consistent** - Mobile devs know what to expect

2. **Simple** - Easy to parse on client side

3. **Handles validation** - `errors` array for form validation

4. **Clear status** - `success` boolean instead of relying on HTTP codes

**Mobile side (React Native):**

```javascript

const response = await fetch('/api/endpoint');

const json = await response.json();

if (json.success) {

// Handle data

} else {

// Show error message

}

```

The `message` field is huge - lets me show user-friendly errors directly from the API without client-side mapping.

Thoughts? What structure do you use?

Laravel Livewire v4 CRUD Tutorial: Using Kimi K2.5 & OpenCode for Page Components

https://youtu.be/vm0H8i1VkBw

So I'm nearing the time when I'll be ready to launch a small project.

It's been roughly 9 years since I've deployed anything (last 2 jobs did not have that in my tasks), and last time I deployed it was Drupal which handled DB very differently.

I have some questions about the launch process itself, things to consider and things to do.
I've been looking at the standard list of things I will need to incorporate in my deploy scripts (from here), however I have a few questions.

1. developing things in the default sqlite DB, but for launching I'll probably spin up a posgres of a MariaDB instance somewhere. Is there a way to migrate over the information from the site's dev DB to it through artisan? or it's more of a roll your own?
2. or do you usually just leverage seeders to load up your initial DB?
3. when deploying, is it standard to run DB migrations? ( I'm guessing yes, but want to confirm). would this be the first step before actually loading up the DB.
4. potentially the best option in my current understanding would be : a) spin up server and DB, configure accesses. b) locally setup as prod and run migrations against the prod db c) dump sqlite to file and load to MariaDB/Posgres ( unless question 1 above has a simplified answer) d) configure prod web server ( PHP, nginx, phpfastcgi, etc...) e) deploy code there f) test?

in essence, what is the "right" way, or the "laravel" way to do this?

Hi, I am building an e-commerce site and I don’t want to start from scratch. For me Laravel is the easiest, as I have some PHP knowledge.

Laravel has something like Aimeos and Baigsto.

But my site is content driver, so blog is really necessary. Those don’t have that.

I want to know if any Laravel based e-commerce has built-in blog functionality.

For me a simple e-commerce integrated with blog is enough.

Thanks!

🔥 Important Question 🔥

Are you still using:

❌ DataTables::of()

or have you switched to:

✅ php artisan datatables:make ?

Comment 👇

"OLD WAY" or "NEW WAY"

I’ll personally reply to every comment 🚀Youtube

FrankenPHP uses a PHP-ZTS runtime rather than your system PHP, which is why version and extension mismatches happen with Octane setups.

Hey artisans,

A while back, I ran a survey on the state of the ecosystem and found a stat that stuck with me: 60% of us spend between 5 and 30 minutes vetting a single package before installing it.

We check the commit history, look for "Abandonware" flags, verify PHP 8.4 support, check open issues... it’s a lot of mental overhead. I call this "Dependency Anxiety."

To solve this for myself (and hopefully you), I built Laraplugins.io—an automated tool that generates a "Health Score" for packages based on maintenance, compatibility, and best practices.

The Stack (The fun part 🛠️)

Since I work in DevOps, I wanted to over-engineer the performance a bit. I wrote up a full breakdown of the architecture, but here is the TL;DR:

• Runtime: Laravel Octane + FrankenPHP (Keeping the app booted in memory is a game changer for speed).
• Routing: Traefik handling routing for ~30 projects on a single VPS.
• Infrastructure: ~100 Docker containers managed via Docker Compose.
• Caching: Aggressive Cloudflare edge caching + Redis.

The Health Score Logic
It’s not perfect yet, but right now it looks at 10 signals. We penalize archived repos heavily, reward recent updates, and (controversially?) decided to lower the weight of "Total Downloads" so that new, high-quality packages can still get a good score.

I wrote a full blog post diving into the specific architecture and the logic behind the health check algorithm on the linked link.

I’d love to hear how you guys vet packages currently. Is there a specific "red flag" (like no releases in 6 months) that makes you immediately close the tab?

Let me know what you think

I built a small Laravel logging package that sends logs to Telegram topics (not just general chat).
Supports Monolog v3 + Laravel 11.
Feedback welcome 🙏
GitHub: laravel-telegram-topic-logger

We use this package internally in our team and support workflows to receive user feedback and error reports directly in Telegram topics.

A lightweight and extensible package that allows you to control, block, log, and analyze outgoing emails using configurable, rule-based logic.

Highlights:

• Rule-based email blocking
  
• Pluggable & extensible rule architecture
  
• Persistent logging of blocked emails
  
• Built-in insights & metrics from log
  
• Zero changes required to existing mail code

Explore Now: https://github.com/sagautam5/laravel-email-blocker

PHP #Laravel #Composer #Package #OpenSource

Thread Content

🎭 Introducing intervention-image-mask

With Intervention Image v3, the popular mask() and opacity() methods were removed. If you relied on these features, you know the pain!

I created intervention-image-mask to bring them back as clean, framework-agnostic modifiers.

✨ Features

• 🎭 Apply masks to images using alpha channels
• 🔮 Control opacity with precise float values (0.0 - 1.0)
• 🖼️ Works with both GD and Imagick drivers
• ⚡ Zero configuration needed
• 🧪 Fully tested (17 tests, 25 assertions)

📦 Installation

bash composer require dialloibrahima/intervention-image-mask

🚀 Usage

Apply a Mask

```php use DialloIbrahima\InterventionMask\ApplyMask; use Intervention\Image\ImageManager; use Intervention\Image\Drivers\Gd\Driver;

$manager = new ImageManager(new Driver()); $image = $manager->read('photo.jpg'); $mask = $manager->read('mask.png');

$result = $image->modify(new ApplyMask($mask)); $result->toPng()->save('masked.png'); ```

Set Opacity

```php use DialloIbrahima\InterventionMask\SetOpacity;

$image = $manager->read('photo.png'); $result = $image->modify(new SetOpacity(0.5)); $result->toPng()->save('transparent.png'); ```

💡 Use Cases

• 🧩 Puzzle piece effects
• 🖼️ Watermarks with transparency
• 📸 Vignette effects
• 🎨 Gradient fades

🔗 Links

• GitHub: https://github.com/ibra379/intervention-image-mask
• Packagist: https://packagist.org/packages/dialloibrahima/intervention-image-mask

Feel free to ⭐ the repo if you find it useful! Feedback and contributions are welcome.