Documenting code, one commit at a time.
In multi-tenant applications built with Filament, ensuring the correct tenant context is crucial for data isolation and application functionality. A common issue arises when middleware responsible for setting the tenant context runs before Filament resolves the tenant from the URL.
In the Reimpact/platform project, a recent update addresses an issue where Livewire update requests were being incorrectly blocked by a custom middleware. This post details the problem and the solution implemented.
The ValidationUserMiddleware was designed to handle user authentication and validation for incoming requests. However, it was inadvertently blocking unauthenticated
In a Laravel application, particularly when using Livewire, maintaining consistent authentication behavior across different types of requests can be tricky. A common issue arises when Livewire requests, which often send Content-Type: application/json, are not correctly handled by authentication middleware, leading to unexpected 401 errors instead of redirects to the login page.
Experiencing a 401 Unauthorized error immediately after a successful login can be a frustrating issue in Laravel applications. This often stems from incorrect redirection targets or misconfigured middleware. Let's explore how to diagnose and resolve such problems, specifically within the context of projects using middleware for access control.
The Reimpact platform is undergoing improvements in how it manages tenant schemas and streamlines database refreshing. These changes aim to improve data consistency, developer experience, and overall system maintainability.
Several updates have been made to how tenant schemas are populated and managed:
The landing project focuses on creating engaging user experiences. Recent work has concentrated on refining data storage and ensuring application stability.
A recurring issue involved PostgreSQL's inability to efficiently use DISTINCT with JSON columns. This manifested as numerous daily errors, particularly within the Campaign editor's
When working with database migrations and seeders in Laravel, particularly with PostgreSQL, developers sometimes encounter issues related to SQL parsing. One such issue arises when attempting to seed data into a table that already exists but is missing a specific column.
When performing database migrations, especially in multi-tenant environments, it's crucial to ensure all aspects of the schema are correctly applied to each tenant. This post explores a scenario in a Laravel application where PostgreSQL functions were unintentionally dropped during a tenant migration and how they were recovered.
When working with databases, especially PostgreSQL, ensuring data integrity during the seeding process is crucial. A common pitfall involves SQL escaping issues, particularly when dealing with special characters within string values.
Initial attempts to populate a database often involve seed migrations. These migrations contain SQL statements to
When building a multi-tenant application with Laravel and PostgreSQL, handling data isolation is crucial. One effective approach is to use separate database schemas for each tenant. This provides a high level of isolation, ensuring that data from different tenants remains completely separate. Let's explore how this works in practice within the Reimpact platform.
