Documenting code, one commit at a time.
The landing project focuses on creating a seamless user experience. A recent enhancement involved improving email notifications to provide more clarity and a better call-to-action.
The update addresses two key areas: visual consistency and ease of navigation. The email footer's color was previously inconsistent with the header, using a darker shade
The Reimpact platform utilizes Filament for its admin panels. A recent update addressed an issue where the impersonation banner wasn't rendering correctly across all panels.
The bg-warning-500 class in Filament relies on CSS custom properties. These properties weren't consistently available during the BODY_START render hook, leading to inconsistent banner styling.
The Reimpact/platform project encountered challenges during data synchronization, specifically with foreign key constraints and memory exhaustion issues. This post outlines the problem, the solution implemented, and key takeaways for managing large-scale data transfers.
During the synchronization of a large dataset (1.45M rows) from a production MySQL database
Maintaining compatibility across different database systems and ensuring code consistency can be challenging in large Laravel projects. This post outlines how the Reimpact/platform project addressed these issues, specifically focusing on PostgreSQL compatibility and tenant table management.
When developing applications that need to support multiple database
We've been working on the Reimpact/platform project, and recently tackled a significant refactoring of our database schema. Our initial design had a mix of shared and module-specific tables within each tenant schema, which led to some challenges as the platform grew.
The primary goal of this refactoring was to improve modularity and maintainability by clearly separating module-specific data.
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.
Row-level multi-tenancy in MySQL, while initially simpler to
Migrating data between different database systems can be a complex undertaking. Recently, the team working on the platform navigated a significant data migration from MySQL to PostgreSQL. This post outlines some key considerations and challenges encountered during the process. These insights can help you avoid common pitfalls when undertaking similar migrations.
This post highlights recent enhancements to the Breniapp interface, focusing on visual refinements and improved user interactions within the application.
A subtle but important fix addresses a visual artifact in the sidebar. When the sidebar collapses, the separator line now transitions smoothly using Filament's CSS variables.
Setting up a local development environment can often be a hurdle, especially when dealing with database credentials. Manually managing these credentials and ensuring they match the production environment can be time-consuming and error-prone. This is especially true for the Reimpact platform, where consistency between development and production environments is crucial.
When building multi-tenant applications with Laravel, managing database schemas for each tenant can become complex. We recently improved our tenant schema population process in the platform project to handle various edge cases and ensure data integrity across companies.
Our initial schema population process had several limitations:
