Introduction

In multi-tenant Laravel applications, queued jobs that interact with tenant-specific data can sometimes fail due to issues with model serialization and tenant context. Specifically, jobs that serialize Eloquent models might attempt to deserialize them outside of the correct tenant's database connection, leading to ModelNotFoundException errors.

Introduction

The Reimpact platform is undergoing improvements to its multi-tenancy architecture, specifically focusing on tenant warehouse management. This involves refining database queries and updating tenant schemas for better isolation and data integrity.

The Problem

Previously, the GeneratedReportResource was incorrectly querying the company_id on tenant-specific warehouse

Introduction

When building multi-tenant applications with Laravel, ensuring proper tenant context and efficient file handling are critical. Recent updates to the Reimpact platform focus on improving these aspects, streamlining tenant schema management and simplifying large file uploads.

Tenant Schema Isolation Improvements

Proper tenant schema isolation is essential for maintaining data

In modern Laravel projects, choosing the right tools is crucial for efficient development and maintainability. The Reimpact/platform project is undergoing a transition from Nova to Filament, aiming to leverage Filament's capabilities for streamlined administration interfaces. This transition impacts testing strategies, requiring a shift from Nova-specific tests to those aligned with Filament.

When developing multi-tenant applications using Laravel, maintaining schema consistency across tenants is crucial. A recent fix in the Reimpact platform addressed an issue where the products table in tenant schemas was missing specific columns, leading to job failures.

The Problem: Missing Columns

The RefreshRecipeWeights job was failing because the recipe_weight and

In the Reimpact/platform project, we're constantly striving for a cleaner, more maintainable codebase. Recently, we undertook a refactoring effort focused on removing unnecessary relationships, improving widget functionality, and ensuring data consistency across tenants.

Removing Non-Existent Relationships

One area identified for improvement was the MassiveUploadWithErrorsResource.

When working with UI frameworks like Filament in Laravel projects, you sometimes encounter situations where the framework's CSS pipeline interferes with custom styling. We recently ran into this issue in the Reimpact platform while developing the QuickLinksWidget.

Filament, being based on Tailwind CSS, compiles its own version of Tailwind. This can lead to inconsistencies if your project's

Introduction

When developing multi-tenant applications using Laravel, managing database schemas can become complex. Each tenant might require specific customizations, including additional columns in existing tables. This post addresses how to handle such scenarios by focusing on adding a homologation_level column to a products table within a tenant-specific schema in the Reimpact platform.

Introduction

Effective communication is crucial for any application. This post explores the new system email management features added to a Laravel project, focusing on centralizing email configurations and streamlining marketing workflows.

Centralized Email Management

One key improvement is the creation of a centralized page for managing system emails. This provides a single point to

Introduction

Maintaining a stable and performant application requires constant attention to detail. This post highlights several key improvements made to a Laravel project, focusing on resolving PHPStan errors, fixing test failures, and preventing database deadlocks. These changes contribute to a more robust and reliable application.

Addressing Static Analysis Errors

Static analysis