In the Reimpact/platform project, we encountered a tricky issue with queue deserialization in our multi-tenant environment. This post details the problem, our investigation, and the solution we implemented.

The Problem

Our application uses a queue to generate reports. A GenerateReportJob is dispatched, serializing the GeneratedReport model.

The Reimpact/platform project focuses on providing a multi-tenant application structure. Recently, we encountered an issue with tenant database schemas being reset prematurely during Livewire updates. This post dives into the problem and the solution implemented.

The Problem

In a multi-tenant application, each tenant typically has its own database schema. We use middleware to set the correct

Introduction

In multi-tenant applications built with Filament, ensuring the correct tenant context is crucial for data isolation and security. A recent fix in the platform addresses an issue where Livewire update requests bypassed Filament's tenant middleware, potentially leading to incorrect schema resolution for super admin users.

Introduction

When building multi-tenant applications with Laravel and Filament, it's crucial to ensure that operations are performed within the correct tenant context. This post addresses a common issue encountered when using Filament's massive upload feature where the tenant context was not active during Livewire form submissions, leading to data integrity violations.

The Problem: Tenant

Keeping dependencies up-to-date can be a headache, especially when upgrading major versions of frameworks. Let's look at how recent changes in the Reimpact platform addressed a namespace change in Filament v5 and improved tenant context resolution.

The Challenge: Filament v5 Namespace Update

Filament is a popular Rapid Application Development (RAD) framework for Laravel.

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

Introduction

Content Security Policy (CSP) is a crucial layer of defense against various types of attacks, including Cross-Site Scripting (XSS). However, sometimes certain routes or functionalities within an application require inline assets or scripts that are not compatible with strict CSP rules.

Introduction

In single-page applications built with frameworks like Livewire, maintaining the correct user locale across all interactions can be tricky. The Breniapp project encountered an issue where the user interface language would revert to the browser's default (often English) during AJAX requests, even if the user had initially selected a different language.

The Problem: Locale

Introducción

En el proyecto landing, estamos mejorando la manera en que gestionamos las cookies de localización. Específicamente, hemos abordado un problema donde la cookie encriptada que guarda la localización del usuario podía fallar al desencriptarse entre diferentes despliegues o cuando Cloudflare interceptaba las redirecciones.

Introduction

When building internationalized applications, handling user locales correctly is crucial. This post delves into how to validate and securely manage locale settings in PHP applications, focusing on preventing potential issues arising from stale or malformed locale data.

The Problem: Stale Locale Cookies

Encrypted cookies, particularly those storing locale information, can