The Reimpact platform is undergoing a significant architectural shift, moving from a MySQL row-level multi-tenancy model to a more robust PostgreSQL schema-per-tenant setup. This post dives into the key considerations and steps involved in this migration, leveraging Laravel and Filament.

The Motivation for Schema-Based Tenancy

Row-level multi-tenancy in MySQL, while initially simpler to

This post dives into a recent architectural enhancement in the Reimpact platform, focusing on improved modularity and service management.

The Need for Modularity

As the Reimpact platform evolves, the need for a more modular architecture becomes crucial. A modular design allows for independent development, easier maintenance, and better scalability.

The platform project is undergoing a series of updates to enhance its architecture and developer experience.

Streamlining Panel Providers

Component registration is now more organized. The PackagingPanelProvider has been registered, ensuring that necessary components are readily available throughout the application. This centralizes the management of UI elements, improving maintainability.

Introduction

Row-level filtering is common for multi-tenancy, but what if you need stronger isolation? At Reimpact's platform, we're migrating towards PostgreSQL schemas to achieve true tenant separation, leveraging Laravel, Filament, and the middleware pattern.

This post details our approach to dynamically setting the PostgreSQL search_path for each tenant, ensuring data isolation and

Introduction

Have you ever wanted to add a unique touch to your Filament admin panels? A simple way to do this is by customizing the favicon. This post will guide you through how the Reimpact platform is streamlining this process using a shared branding trait.

The Problem: Consistent Branding

Maintaining consistent branding across multiple Filament panels can be challenging.

Introduction

When building multi-tenant applications, choosing the right architecture is critical. This post explores how to leverage PostgreSQL schemas within a Laravel application to achieve tenant isolation, enhance security, and improve scalability.

The Multi-Tenant Challenge

Traditional multi-tenant approaches often involve sharing a single database and distinguishing tenants by a

The Reimpact platform is undergoing a transition of its module URLs from Nova to Filament. This post details how we fixed a login redirect issue that arose during this migration.

The Problem

After migrating the Packaging module to Filament, users were experiencing redirect issues upon login when the MODULE_SELECTOR_SYSTEM feature flag was enabled.

When working on collaborative projects like the landing page project, merge conflicts are almost inevitable. Understanding how to resolve them effectively is crucial for maintaining a smooth workflow.

Understanding Merge Conflicts

Merge conflicts arise when multiple developers modify the same lines of a file or when one developer modifies a file while another deletes it.

Introduction

In the Breniapp/brenia project, we're continuously working to improve the user interface and overall user experience. One recent focus has been on optimizing the layout of Filament admin panel pages, particularly in scenarios where a more compact design is desired.

The Challenge: Vertical Space Optimization

Filament, a PHP-based admin panel, offers a flexible and

In the Reimpact platform, we're constantly striving for a cleaner, more maintainable codebase. Recently, we tackled an area involving rates and their association with different modules within the system.

The Problem: Priority Products and Foreign Keys

Originally, rates were tied to "priority products" using a foreign key relationship. This approach, while seemingly straightforward,