Documenting code, one commit at a time.
When building multi-tenant applications with Laravel and Filament, it's crucial to ensure that operations are performed within the correct tenant context. This post addresses a common issue encountered when using Filament's massive upload feature where the tenant context was not active during Livewire form submissions, leading to data integrity violations.
Ensuring background jobs are correctly dispatched and optimizing resource allocation are critical for application stability and performance. This post explores recent enhancements to a Filament-based platform, focusing on ensuring consistent job dispatch across modules and improving worker allocation for resource-intensive tasks.
Keeping dependencies up-to-date can be a headache, especially when upgrading major versions of frameworks. Let's look at how recent changes in the Reimpact platform addressed a namespace change in Filament v5 and improved tenant context resolution.
Filament is a popular Rapid Application Development (RAD) framework for Laravel.
The Reimpact platform has undergone an update to align with Filament v5, specifically addressing changes in how actions are handled within tables. This adjustment ensures compatibility and leverages the latest features offered by the framework.
In previous versions of Filament, actions within tables were managed using Tables\Actions\Action.
The Reimpact platform is undergoing improvements to its multi-tenancy architecture, specifically focusing on tenant warehouse management. This involves refining database queries and updating tenant schemas for better isolation and data integrity.
Previously, the GeneratedReportResource was incorrectly querying the company_id on tenant-specific warehouse
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
In modern Laravel projects, choosing the right tools is crucial for efficient development and maintainability. The Reimpact/platform project is undergoing a transition from Nova to Filament, aiming to leverage Filament's capabilities for streamlined administration interfaces. This transition impacts testing strategies, requiring a shift from Nova-specific tests to those aligned with Filament.
Effective communication is crucial for any application. This post explores the new system email management features added to a Laravel project, focusing on centralizing email configurations and streamlining marketing workflows.
One key improvement is the creation of a centralized page for managing system emails. This provides a single point to
In the Breniapp/brenia project, we've been focusing on improving the user experience within our Filament-based admin panel. One recent enhancement involved strategically relocating the 'autoplanificar' (auto-planner) button to a more intuitive location within the Filament page.
This post details the rationale behind this change and the technical considerations involved.
El proyecto landing se enfoca en mejorar la interacción en LinkedIn mediante el uso de inteligencia artificial. Se ha desarrollado una funcionalidad para asistir en la generación de respuestas contextuales, optimizando la comunicación y ahorrando tiempo a los usuarios.
Responder de manera efectiva y personalizada en LinkedIn puede ser un desafío, especialmente
