The Challenge

Managing various data entities within a complex application can become unwieldy without a structured approach. We needed a consistent and efficient way to handle data presentation, creation, and modification across different areas of the Reimpact platform.

The Solution

We leveraged Filament, a rapid application development framework for Laravel, to migrate and centralize

The Reimpact platform focuses on streamlining various business processes. A recent enhancement involves adding Filament resource pages for secondary modules to improve the user interface and data management.

Enhanced Module Management

This update introduces List, Create, Edit, and View pages for several modules, including AEEAndCells, Batteries, and Tires.

Building robust and scalable applications often involves modular design principles. In the Reimpact/platform project, we've been focusing on enhancing our Filament resource implementations to streamline development and improve maintainability across various modules.

Streamlining Module Development with Filament

Filament provides a powerful way to create admin panels for Laravel applications.

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

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.

The devlog-ist/landing project focuses on creating a smooth and reliable user experience. Recent work has addressed several critical production errors to enhance stability and prevent disruptions.

Addressing Production Errors

Production errors can significantly impact user satisfaction and overall application performance. A proactive approach to identifying and resolving these issues is

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.

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.

The Problem

In the Reimpact platform, we encountered an issue where session validation middleware was causing unexpected logouts during user impersonation. Specifically, the CheckValidSession and EnsureSingleSession middlewares were interfering with the impersonation process, leading to a frustrating user experience.

The Cause

The root cause of the problem lies in how the session is