Forem: Jiordi Viera

I built a Laravel package to stop silent cron failures

Jiordi Viera — Wed, 10 Dec 2025 17:21:30 +0000

My backup job failed at 3 AM last month. I found out on Monday when a client asked why their data wasn't updated.

This kept happening. Sync tasks stuck for hours. Report generation failing silently. No notifications, no logs I could easily check.

So I built something to fix it.

What I built

Laravel Smart Scheduler tracks every scheduled task execution automatically. Install it, and you get:

Execution history for every task
Stuck task detection (when server crashes mid-task)
Email notifications on failure
Overlap prevention with visibility

composer require jiordiviera/laravel-smart-scheduler
php artisan vendor:publish --tag=smart-scheduler-migrations
php artisan migrate

No changes to your existing tasks. It hooks into Laravel's events.

How it works

Every execution gets recorded:

use Jiordiviera\SmartScheduler\LaravelSmartScheduler\Models\ScheduleRun;

// Recent executions
$runs = ScheduleRun::latest('started_at')->limit(10)->get();

// What failed
$failed = ScheduleRun::where('status', ScheduleRun::STATUS_FAILED)->get();

Each record has: task identifier, status, start/end time, duration, output, exception message, server name.

Stuck task detection

This is the feature I needed most.

When your server crashes or a process gets killed, the task stays in "starting" status. Next run sees an overlap and skips. Your task never runs again until you manually fix it.

Smart Scheduler detects this:

// config/smart-scheduler.php
'stuck_timeout_minutes' => 60,

When a new execution starts, it checks for old "starting" tasks past the timeout, marks them as "stuck", notifies you, and lets the new execution proceed.

You can also run it manually:

php artisan smart-scheduler:detect-stuck

Notifications

// config/smart-scheduler.php
'notifications' => [
    'email' => [
        'recipients' => ['admin@example.com'],
    ],
    'notify_on_stuck' => true,
],

Or in your .env:

SMART_SCHEDULER_EMAIL_RECIPIENTS=admin@example.com

Setup I recommend

// routes/console.php
use Illuminate\Support\Facades\Schedule;

// Clean old records weekly
Schedule::command('smart-scheduler:purge')->weekly();

// Detect stuck tasks every 30 minutes
Schedule::command('smart-scheduler:detect-stuck')->everyThirtyMinutes();

Custom notifications

Want Slack instead of email? Implement the interface:

use Jiordiviera\SmartScheduler\LaravelSmartScheduler\Contracts\SmartNotifierInterface;

class SlackNotifier implements SmartNotifierInterface
{
    public function sendFailureNotification(ScheduleRun $run): void
    {
        // Your Slack logic
    }

    public function sendStuckNotification(ScheduleRun $run): void
    {
        // Your Slack logic
    }
}

// In a service provider
$this->app->singleton(SmartNotifierInterface::class, SlackNotifier::class);

Requirements

PHP 8.2+
Laravel 11 or 12

L'Injection de Dépendances (DI) : Comment le Service Container de Laravel Vous Rend Invincible

Jiordi Viera — Tue, 11 Nov 2025 22:53:04 +0000

Avouons-le : quand on commence avec Laravel, on voit le terme "Injection de Dépendances" (DI), on lève les yeux au ciel, et on se dit que c'est du jargon d'architecte. Erreur monumentale! La DI, c'est le super-pouvoir que le Service Container de Laravel vous donne pour écrire du code qui ne vous fera pas hurler à 3h du matin.

Oubliez la théorie. Concentrons-nous sur un seul objectif : écrire du code flexible et facile à tester. Prêt ? C'est parti.

1. Le Couplage Fort : Le Ciment qui Tue Votre Code

Pourquoi se compliquer la vie ? Regardez ce code qui semble simple, mais qui est un véritable piège.

🛑 Le Piège du "Je me débrouille tout seul"

Imaginez un service qui doit gérer le paiement.


class OrderProcessor
{
    public function process(Order $order)
    {
        // ❌ Problème : Le OrderProcessor est collé à Stripe.
        $gateway = new StripePaymentGateway(); 
        $gateway->charge($order->total);

    }
}

Pourquoi ce code est toxique ?

Changement = Catastrophe : Votre boss arrive : "On passe à PayPal la semaine prochaine !". Vous devez aller modifier directement ce fichier. Et s'il y a 20 endroits qui utilisent StripePaymentGateway ? 😩
Tester est un cauchemar : Comment tester la logique de process() sans déclencher un vrai paiement chez Stripe ? Vos tests unitaires deviennent des tests d'intégration, ils sont lents, chers, et dépendent d'une connexion Internet.

Le principe pour s'en sortir ? L'Inversion de Contrôle (IoC). Au lieu que votre classe crie "Je veux Stripe!", c'est le système qui lui dit : "Tiens, voilà ton outil de paiement. Utilise-le."

2. Le Service Container : Le Cerveau de Laravel

Le Service Container est l'usine centralisée qui gère cette inversion de contrôle. Il sait comment construire chaque objet et où le livrer.

A. La Magie Noire : La Résolution Automatique

Vous utilisez la DI tous les jours sans vous en rendre compte. C'est la forme la plus simple, basée sur le type-hinting :

class OrderProcessor
{
    protected StripePaymentGateway $gateway;

    // ✨ Le Conteneur voit 'StripePaymentGateway', le crée et l'injecte.
    public function __construct(StripePaymentGateway $gateway)
    {
        $this->gateway = $gateway;
    }
}

Boom! Laravel a lu votre besoin, l'a résolu, et vous l'a servi sur un plateau d'argent.

B. Le Saint Graal : Les Bindings et les Interfaces

C'est la partie qui sépare les amateurs des pros. Le code ci-dessus est bien, mais il est toujours attaché à la classe concrète StripePaymentGateway. Pour la flexibilité ultime, il faut dépendre d'une Interface (un contrat).

On Configure l'Usine (Dans un Service Provider)

Nos Service Providers sont l'endroit où nous faisons le lien. Nous disons au conteneur : "Quand quelqu'un demande le Contrat (Interface), donne-lui cette Implémentation."

// App/Providers/AppServiceProvider.php

use App\Contracts\PaymentGateway;
use App\Services\StripePaymentGateway;

public function register(): void
{
    // 💡 Binding : Demande l'Interface (le "Quoi"), donne l'Implémentation (le "Comment").
    $this->app->bind(
        PaymentGateway::class,
        StripePaymentGateway::class // On peut changer cette ligne pour PayPal
    );
}

Le Code de l'OrderProcessor Devient Parfait

Notre processeur ne demande plus Stripe, il demande N'IMPORTE QUEL outil de paiement qui respecte le contrat :

class OrderProcessor
{
    protected PaymentGateway $gateway; // Type-hinting vers l'INTERFACE

    public function __construct(PaymentGateway $gateway)
    {
        // 🥳 C'est le conteneur qui décide si c'est Stripe, PayPal, ou un Mock de test.
        $this->gateway = $gateway;
    }
    // ...
}

Le bénéfice immédiat : Pour tester OrderProcessor, vous n'avez qu'à injecter un Mock de PaymentGateway qui simule la réponse de paiement. Vos tests sont rapides, isolés, et fiables.

3. Le Data Binding : La DI dans l'URL

Laravel étend cette philosophie géniale aux données de la requête via le Route Model Binding. C'est une DI spécifique au contexte web.

A. Oubliez les ID avec le Binding Implicite

Combien de fois avez-vous écrit ça ? Post::findOrFail($id);... Assez !

// routes/web.php
Route::get('/posts/{post}', [PostController::class, 'show']);

// App/Http/Controllers/PostController.php
public function show(Post $post) //  Injection directe du modèle !
{
    // Le conteneur a lu l'URL, trouvé le Post correspondant, et l'a injecté. 
    // Si le post n'existe pas, Laravel envoie un 404 tout seul. Propre.
    return view('posts.show', compact('post'));
}

Le conteneur lit le Post $post, comprend qu'il doit récupérer l'objet depuis la base de données, et l'injecte. C'est la beauté du code déclaratif.

B. Le Cas du Slug

Vous ne voulez pas utiliser l'ID ? Pas de problème. Dites à Laravel quelle clé utiliser en ajoutant une seule méthode dans votre modèle :

// App/Models/Post.php
public function getRouteKeyName(): string
{
    return 'slug'; // On utilise le 'slug' au lieu de 'id' dans l'URL
}

Et ça marche ! Le Data Binding se mettra à jour automatiquement.

Conclusion : Adoptez la Mentalité DI

L'Injection de Dépendances dans Laravel, ce n'est pas une complexité à éviter, c'est l'ensemble d'outils (Conteneur, Bindings, Data Binding) qui vous force à coder avec des contrats.

Ce passage aux Interfaces et aux Service Providers est ce qui transforme un développeur junior qui suit les tutoriels en un architecte senior capable de bâtir une application modulaire et qui ne craint pas le changement.

Pour vos prochains services métier (Notifications, Export, Paiement), commencez toujours par définir l'Interface avant l'implémentation. Le Service Container est votre meilleur ami, utilisez-le!

Laravel Log Cleaner v2.01 - Memory-Efficient Log Management with Compression & Backup

Jiordi Viera — Thu, 06 Nov 2025 02:57:00 +0000

Laravel Log Cleaner v2.0 - Memory-Efficient Log Management

The Problem 🔥

We've all been there: your Laravel app runs fine for weeks, then suddenly your server runs out of disk space. You SSH in, check the logs folder, and find a 5GB laravel.log file.

Sound familiar?

Log files can grow out of control fast, especially in production. But clearing them manually is risky, and heavy monitoring tools like Telescope can slow down your app or even crash your server.

The Solution ✨

I built Laravel Log Cleaner to solve this exact problem. Version 2.0 just launched with major improvements:

🧠 Memory-efficient processing - handles multi-GB files without crashing
📦 Compression support - archive old logs instead of deleting
🔒 Backup creation - never lose important data
🎯 Log level filtering - keep only ERROR logs, discard the rest
👀 Dry-run mode - preview changes before applying
⚡ 50%+ performance improvement on large files

Installation

composer require jiordiviera/laravel-log-cleaner

That's it! No config files, no service providers to register. Laravel's auto-discovery handles everything.

Basic Usage

Clear all logs:

php artisan log:clear

Keep the last 30 days:

php artisan log:clear --days=30

Advanced Features (What's New in v2.0)

1. Safe Operations 🔒

Preview what will be deleted without actually deleting:

php artisan log:clear --days=30 --dry-run

Output:

[DRY RUN] Would remove 15,420 lines from laravel.log
[DRY RUN] Estimated space to free: 45.2 MB

Create a backup before cleaning:

php artisan log:clear --days=30 --backup

Output:

Backup created: storage/logs/laravel.log.backup.2024-11-05-14-30-15
Logs older than 30 days have been removed.

2. Compression Instead of Deletion 📦

Archive old logs for compliance or audit purposes:

php artisan log:clear --days=30 --compress

This creates laravel.log.old.2024-11-05.gz - perfect for when you need to keep logs but save disk space.

3. Log Level Filtering 🎯

Keep only critical errors, discard everything else:

php artisan log:clear --days=0 --level=ERROR

This is huge for production. Most of your logs are probably DEBUG or INFO - useful during development but just noise after a few days in production.

Supported levels: DEBUG, INFO, WARNING, ERROR, CRITICAL

4. Memory-Efficient Processing 🧠

The game-changer for huge log files:

php artisan log:clear --days=30 --memory-efficient

Before v2.0: A 2GB log file would crash PHP with "out of memory" errors

After v2.0: Processes the same file using stream processing, never loads more than 50MB in RAM

The package automatically detects large files (>50MB) and enables memory-efficient mode, but you can force it with this flag.

5. Custom Date Patterns 🔍

Got non-standard log formats? No problem:

php artisan log:clear --days=30 --pattern="/^(\d{4}-\d{2}-\d{2})/"

6. Combine Everything 🚀

The complete workflow:

php artisan log:clear --days=30 --backup --compress --level=ERROR --dry-run

This command:

Previews what would be deleted (dry-run)
Creates a backup before making changes
Compresses old logs instead of deleting
Keeps only ERROR level logs

Real-World Use Case

Here's how I use it in production:

Laravel 11+ (Current)

Schedule in routes/console.php:

use Illuminate\Support\Facades\Schedule;

// Every day at 2 AM - keep 7 days of ERROR logs
Schedule::command('log:clear', [
    '--days' => 7,
    '--backup' => true,
    '--level' => 'ERROR'
])->daily()->at('02:00');

// Weekly deep clean with compression
Schedule::command('log:clear', [
    '--days' => 30,
    '--compress' => true
])->weekly()->sundays()->at('03:00');

Laravel 10 and Below

Schedule in app/Console/Kernel.php:

protected function schedule(Schedule $schedule)
{
    $schedule->command('log:clear', [
        '--days' => 7,
        '--backup' => true,
        '--level' => 'ERROR'
    ])->daily()->at('02:00');

    $schedule->command('log:clear', [
        '--days' => 30,
        '--compress' => true
    ])->weekly()->sundays()->at('03:00');
}

Result:

✅ Keeps 7 days of ERROR logs for quick debugging
✅ Archives everything older in compressed format
✅ Never runs out of disk space
✅ No manual intervention needed
✅ Backups created automatically

Performance Benchmarks 📊

I tested this on a real production log file from one of my client's projects:

Test File: 1.2 GB, 3.5 million lines

Operation	v1.0	v2.0	Improvement
Clear all logs	45s	12s	73% faster ⚡
Filter by date (30 days)	Memory error ❌	18s	Now possible ✅
Memory usage (peak)	512MB+	48MB	90% reduction 🎯
Compression	Not supported	8s	New feature 🆕

Why Not Use X? 🤔

vs. Manual deletion (`rm laravel.log` or `echo "" > laravel.log`)

❌ No selective date filtering
❌ Risk of deleting current day's logs
❌ No backup option
❌ Can't filter by log level

vs. Laravel Telescope

❌ Telescope is heavy (database overhead, UI, background jobs)
❌ Can actually slow down your app in production
✅ Laravel Log Cleaner has zero runtime overhead
✅ Only runs when you schedule it

vs. Other log cleaner packages

Most alternatives:

❌ Don't handle memory efficiently (crash on large files)
❌ No compression support
❌ No log level filtering
❌ No dry-run mode for safety
❌ Limited or no backup functionality

Compatibility

Current Version (v2.x):

PHP 8.1, 8.2, 8.3+
Laravel 9.x, 10.x, 11.x, 12.x

Legacy Support (v1.x):
If you're still on older versions:

composer require jiordiviera/laravel-log-cleaner:^1.0

PHP 7.0+
Laravel 7.x, 8.x

Migration from v1.x

Upgrading from v1.x? It's seamless!

Step 1: Update via Composer

composer update jiordiviera/laravel-log-cleaner

Step 2: Check PHP/Laravel requirements

Requires PHP 8.1+
Requires Laravel 9+

Step 3: Enjoy new features!
All your existing commands still work. The new features are opt-in via command flags.

Breaking changes:

Dropped PHP 7.x support
Dropped Laravel 7.x and 8.x support
If you need these versions, stay on v1.x

Common Use Cases

1. Development: Keep Recent Logs Only

php artisan log:clear --days=3

2. Production: Aggressive Cleanup with Safety

php artisan log:clear --days=7 --backup --level=ERROR

3. Compliance: Archive Everything

php artisan log:clear --days=90 --compress

4. Emergency: Server Running Out of Space

# Preview impact first
php artisan log:clear --days=1 --dry-run

# If safe, execute
php artisan log:clear --days=1 --backup

5. CI/CD Pipeline: Clean After Tests

php artisan log:clear --days=0

What's Next? 🔮

I'm considering these features for future releases:

🗂️ Multiple log file support (--file=api.log)
📧 Slack/Email notifications on cleanup completion
⚙️ Config file for environment-specific retention policies
☁️ Cloud storage integration (S3, GCS, Azure)
📊 Log analytics before cleanup (show stats)
🔄 Auto-rotation based on file size (not just days)

What would YOU like to see? Drop a comment below! Your feedback shapes the roadmap.

Try It Out

composer require jiordiviera/laravel-log-cleaner
php artisan log:clear --help

Links:

📦 Packagist
🐙 GitHub Repository
⭐ Star on GitHub if you find it useful!

Contributing

Found a bug? Have a feature request? Contributions are welcome!

Fork the repo
Create a feature branch
Write tests (we use Pest)
Submit a PR

Check out the Contributing Guide.

About Me

I'm Jiordi Viera, a fullstack developer from Douala, Cameroon 🇨🇲. I work primarily with Laravel, Next.js, and React.

I built this package after dealing with production log issues one too many times. What started as a simple script evolved into a full package when I realized others had the same problem.

If this package helps you, consider:

⭐ Starring the GitHub repo
📢 Sharing this article
☕ Buying me a coffee (if you're feeling generous)

Connect with me:

🌐 Website: jiordiviera.me
🐙 GitHub: @jiordiviera
💼 LinkedIn: [Add your LinkedIn if you have one]
🐦 Twitter/X: [Add your handle if you have one]

Other projects:

Codepit - A minimal platform to share code snippets

Thanks for reading! If you found this helpful, please leave a ❤️ and share your experience in the comments below.

Happy logging! 🚀

Laravel #PHP #OpenSource #DevOps #WebDev #BackendDevelopment

Introducing Codepit: A Minimal Platform to Share Code Snippets

Jiordi Viera — Fri, 05 Sep 2025 15:09:13 +0000

Introducing Codepit: A Minimal Platform to Share Code Snippets

Every developer has a collection of small code snippets saved somewhere — in notes, gists, or random files.

But when it comes to organizing, reusing, and sharing them, things can quickly get messy.

Codepit is a minimal and fast platform to create, share, and organize code snippets in a structured way.

You can try it here: https://codepit.jiordiviera.me

Features

Create and edit snippets with language selection and syntax highlighting
Organize snippets into collections (public or private)
Explore and discover snippets by tags, language, or author
Comments, likes, and view counts
OAuth authentication (guests can browse, sign-in required for interactions)

Tech Stack

Next.js (App Router) + React + TypeScript
TailwindCSS v4 with design tokens
Prisma + PostgreSQL
Monaco Editor for editing, Shiki/Prism for highlighting
Better Auth for authentication
Bun as runtime

Screenshots

Roadmap

Planned improvements include:

Public collections gallery with filters
Rich open graph images per snippet
Like support for comments
Rate-limiting for comment and view tracking

Feedback

Codepit is focused on staying minimal and practical.

I’d love to hear your thoughts:

Which features matter most to you when managing snippets?
Would you use it for public sharing or private storage?

Comments and suggestions are very welcome.

Forem: Jiordi Viera

I built a Laravel package to stop silent cron failures

What I built

How it works

Stuck task detection

Notifications

Setup I recommend

Custom notifications

Requirements

Links

L'Injection de Dépendances (DI) : Comment le Service Container de Laravel Vous Rend Invincible

1. Le Couplage Fort : Le Ciment qui Tue Votre Code

🛑 Le Piège du "Je me débrouille tout seul"

2. Le Service Container : Le Cerveau de Laravel

A. La Magie Noire : La Résolution Automatique

B. Le Saint Graal : Les Bindings et les Interfaces

On Configure l'Usine (Dans un Service Provider)

Le Code de l'OrderProcessor Devient Parfait

3. Le Data Binding : La DI dans l'URL

A. Oubliez les ID avec le Binding Implicite

B. Le Cas du Slug

Conclusion : Adoptez la Mentalité DI

Laravel Log Cleaner v2.01 - Memory-Efficient Log Management with Compression & Backup

Laravel Log Cleaner v2.0 - Memory-Efficient Log Management

The Problem 🔥

The Solution ✨

Installation

Basic Usage

Advanced Features (What's New in v2.0)

1. Safe Operations 🔒

2. Compression Instead of Deletion 📦

3. Log Level Filtering 🎯

4. Memory-Efficient Processing 🧠

5. Custom Date Patterns 🔍

6. Combine Everything 🚀

Real-World Use Case

Laravel 11+ (Current)

Laravel 10 and Below

Result:

Performance Benchmarks 📊

Why Not Use X? 🤔

vs. Manual deletion (rm laravel.log or echo "" > laravel.log)

vs. Laravel Telescope

vs. Other log cleaner packages

Compatibility

Migration from v1.x

Common Use Cases

1. Development: Keep Recent Logs Only

2. Production: Aggressive Cleanup with Safety

3. Compliance: Archive Everything

4. Emergency: Server Running Out of Space

5. CI/CD Pipeline: Clean After Tests

What's Next? 🔮

Try It Out

Contributing

About Me

Laravel #PHP #OpenSource #DevOps #WebDev #BackendDevelopment

Introducing Codepit: A Minimal Platform to Share Code Snippets

Introducing Codepit: A Minimal Platform to Share Code Snippets

Features

Tech Stack

Screenshots

Roadmap

Feedback

vs. Manual deletion (`rm laravel.log` or `echo "" > laravel.log`)