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.

When multiple developers are working on the same project, especially on long-lived feature branches, merge conflicts are inevitable. Let's examine how to approach resolving these conflicts in the landing project.

Understanding the Conflict

Merge conflicts arise when Git is unable to automatically reconcile changes from different branches. This commonly occurs when multiple developers have

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

Introduction

In the fast-paced world of web development, efficient workflow management is key. The landing project benefits from leveraging Git worktrees to enhance developer productivity and reduce context switching overhead.

The Challenge: Context Switching

Developers often juggle multiple features or bug fixes simultaneously. Switching between these tasks traditionally involves

The landing project benefits from a streamlined workflow, focusing on isolating changes and enhancing team collaboration. By adopting worktrees, developers can work on multiple features simultaneously without disrupting the main codebase.

Understanding Worktrees

Worktrees allow you to check out multiple branches of a Git repository into separate directories.

This post explores how merging feature branches can streamline development workflows, enhance collaboration, and improve code quality. We'll focus on the practical benefits and strategies for effective branch management within the devlog-ist/landing project.

The Challenge

In many projects, integrating new features involves complex merging procedures that can become bottlenecks.

This post discusses the process of merging branches in the landing project, focusing on how to handle conflicts that arise during the merge.

The Merge

Recently, a merge operation was performed, bringing together changes from the worktree-agent-a711e2dd branch into the main development branch. This is a standard practice in collaborative software development, allowing developers to

Navigating complex feature development often involves juggling multiple branches, leading to potential conflicts and a cluttered workflow. This is a story about how incorporating worktrees streamlined branch management in a PHP project.

The Challenge

Our team faced difficulties when working on several features concurrently. Switching between branches frequently resulted in lost context,