Documenting code, one commit at a time.
The platform project is undergoing continuous improvement to enhance its notification system.
Initially, the notification system stored data in a simple text column. However, as the platform evolved, the need for richer, structured data within notifications became apparent. This required a transition to a more flexible data type.
The Reimpact platform is focused on streamlining various business processes. Recent updates enhance the platform's interaction with databases, specifically focusing on user notifications and improved error handling for foreign key violations in both MySQL and PostgreSQL.
A key improvement involves enabling database notifications within Filament panels.
The Reimpact/platform project focuses on providing a multi-tenant application structure. Recently, we encountered an issue with tenant database schemas being reset prematurely during Livewire updates. This post dives into the problem and the solution implemented.
In a multi-tenant application, each tenant typically has its own database schema. We use middleware to set the correct
The Reimpact platform is undergoing continuous improvements to enhance its multi-tenancy capabilities. Recent work focuses on optimizing database queries within the Packaging module, ensuring data isolation and preventing errors in tenant-specific schemas.
In a multi-tenant environment, each tenant operates within its own schema. The Packaging module, responsible for managing
In multi-tenant applications, managing data isolation is crucial. The Reimpact platform, designed for managing various industrial processes, initially relied on company_id filtering within each database table to achieve this isolation. This approach, while functional, introduced redundancy and complexity across our Eloquent models.
When building multi-tenant applications with Laravel, ensuring proper tenant context and efficient file handling are critical. Recent updates to the Reimpact platform focus on improving these aspects, streamlining tenant schema management and simplifying large file uploads.
Proper tenant schema isolation is essential for maintaining data
When developing web applications, unexpected errors can sometimes arise from seemingly simple oversights. This post details how a translation issue in the Breniapp project led to a 500 error and how it was resolved.
After a recent update, users reported a 500 error when accessing the /admin page. The error logs indicated an issue related to the __('credits') translation
Maintaining a stable and performant application requires constant attention to detail. This post highlights several key improvements made to a Laravel project, focusing on resolving PHPStan errors, fixing test failures, and preventing database deadlocks. These changes contribute to a more robust and reliable application.
Static analysis
