Documenting code, one commit at a time.
The Reimpact/platform project experienced production crashes due to out-of-memory (OOM) errors. These errors stemmed from the Horizon queue worker consuming excessive memory, particularly on smaller instance sizes.
The default configuration for Supervisor-2, responsible for managing Horizon workers, was allocating substantial memory per worker process.
The landing project aims to provide a seamless user experience. Recent work focuses on a subtle but important distinction: differentiating between public discoverability and direct access to services. Let's dive into the details.
Previously, certain mentor services were hidden from public listings. However, this also inadvertently blocked users from accessing these services
Users of the Reimpact platform were experiencing 401 errors during Livewire POST requests. The investigation revealed that session cookies were not being sent correctly when the application was served over HTTPS. The root cause was identified as the same_site attribute of the session cookie being null while the secure attribute was also false, leading to the browser blocking
When using Laravel Horizon, a queue monitoring tool, you might encounter issues with Content Security Policy (CSP) blocking inline scripts. Here's how to address it.
Horizon serves its JavaScript and CSS inline using Horizon::js() and Horizon::css(). Without a proper nonce for CSP, browsers can block these inline scripts, even though Horizon's own authentication gate
