Documenting code, one commit at a time.
The justifai project is a microservice-based application that initially launched with an open API. As the project evolved, it became crucial to implement robust security measures and comprehensive monitoring to ensure data integrity, user authentication, and system reliability.
On the justifai project, our infrastructure as code (IaC) setup, while functional, presented growing challenges. Initially designed as a flat Terraform configuration, it became increasingly complex to manage, understand, and scale as the project evolved. This monolithic approach obscured resource dependencies, hindered reusability, and increased the cognitive load on developers.
In the realm of dynamic web applications, user-generated content is a double-edged sword: it drives engagement but demands robust moderation. Efficiently reviewing and managing content is critical for maintaining platform quality and user safety. The challenge lies in building a system that is both secure and scalable, allowing administrators to moderate content without friction.
In the Justifai project, maintaining up-to-date and accurate architecture documentation for our evolving serverless environment was a consistent challenge. As features rapidly develop and AWS services are integrated, manual diagrams quickly become stale, leading to misunderstandings and increased onboarding time.
Ever been blocked at the final hurdle of deployment by something as seemingly simple as a file upload? For the justifai project, preparing for an end-to-end demo revealed a common, yet critical, oversight: S3 Cross-Origin Resource Sharing (CORS) configurations. This often overlooked detail can halt browser-based uploads dead in their tracks, especially when using presigned URLs, leading to
Developing a frontend application, specifically for the justifai project, presented an unexpected hurdle: a blank white page immediately after loading. The root cause? A ReferenceError: global is not defined error, stemming from the amazon-cognito-identity-js module.
The amazon-cognito-identity-js library, often used with AWS Amplify for authentication, was originally
In the realm of Single Page Applications (SPAs), a compelling user interface can be a powerful differentiator. For the "justifai" project, we've taken this to heart, embarking on a significant visual transformation to introduce a unique 'dossier administratif' (administrative folder) aesthetic.
In the justifai project, our document processing pipeline relies heavily on AWS Textract for extracting information from various file types. However, a critical issue emerged: when Textract encountered an unsupported document format, such as a PDF that Textract's synchronous API couldn't process, our AWS Lambda function would fail.
In the justifai project, a critical aspect of the dashboard functionality involves managing document statuses, specifically through validation and rejection. These operations require sending PATCH requests to the backend API to update document records. However, users were encountering issues where these updates were unexpectedly failing.
PATCH RequestsIn the ongoing development of the viaops project, recent updates have focused on refining both the end-user experience and developer workflows. These improvements range from subtle UI tweaks to significant CI/CD optimizations, all aimed at making the platform more intuitive and efficient.
The user interface received several thoughtful updates.