Documenting code, one commit at a time.
En el proyecto Reimpact/platform, nos enfocamos continuamente en la estabilidad y fiabilidad de nuestras herramientas internas. Una pieza clave de este ecosistema es la herramienta de homologación, diseñada para asegurar la consistencia y preparación de los entornos de datos, particularmente en configuraciones multi-inquilino.
In our landing project, which orchestrates various background processes, we faced a common but insidious problem: production logs were overflowing with ERROR messages. While diligence about errors is good, these weren't true bugs; they were expected retry exhaustion from jobs interacting with external services, like rate limits or timeouts.
Ensuring the robust deployment of applications is crucial. A common challenge is handling unexpected errors during deployment and ensuring environment variables are correctly utilized. This post explores enhancements to deployment scripts within a platform project to address these issues.
Naive deployment scripts
Recently, users of the Reimpact platform experienced instability in their dashboards. This was due to a combination of data inconsistencies and error handling issues. Specifically, missing data in the public.rates table and unhandled PostgreSQL errors were causing Livewire components to crash, impacting the entire dashboard experience.
In the Breniapp project, we recently encountered a common issue: data type mismatches between form inputs and expected data types in our application logic. This post details how we addressed a specific instance of this problem, focusing on maintaining data integrity and preventing runtime errors.
Filament, a PHP framework, provides convenient form input
