Introduction

This post details a recent dependency update to Lodash within the platform. Lodash is a utility library providing helpful functions for working with arrays, objects, strings, and numbers. Keeping dependencies up-to-date is crucial for maintaining security, performance, and compatibility.

The Update

The platform's Lodash dependency has been bumped from version 4.17.21 to 4.17.

Introduction

Our application initially stored user-specific data directly within the Tenant model. As we've grown, the need for a more scalable and maintainable solution became apparent. To address this, we embarked on a project to separate user profiles into a dedicated table within each tenant's schema.

The Challenge

Storing user data directly in the Tenant model created several

Introduction

Our team has been working on streamlining the video rendering process for our landing page promos. This update focuses on simplifying the output format to a single standard: MP4.

The Change

The previous setup involved generating both MP4 and WebM formats for different browsers and devices. This required maintaining separate rendering configurations and increased storage

The Issue

Users reported that embedded WebM videos on the landing page were not playing correctly across all browsers and devices. This was particularly noticeable with VP9-encoded WebM files.

The Solution

To ensure a consistent and reliable user experience, the decision was made to temporarily remove the problematic WebM video files and rely solely on MP4 versions for video playback.

Introduction

We've increased the retention period for jobs within Laravel Horizon, our Redis-powered queue monitoring dashboard. This enhancement provides a more comprehensive view of queue activity, aiding in debugging and performance analysis.

The Problem

Previously, Horizon was configured to trim recent, pending, and completed jobs after only 60 minutes.

Introduction

We recently adjusted the frequency of our automated synchronization process to improve system responsiveness and data consistency. This post details the change and the reasoning behind it.

The Change

The auto-sync schedule was updated from running hourly to every minute. This adjustment aims to provide near real-time updates for critical data.

Schedule::command('posts

The Issue

The Filament admin panel's sidebar header was not behaving as expected on desktop screens. Specifically, its positioning wasn't sticky, leading to a poor user experience when scrolling through long lists of navigation items.

The Fix

A CSS update was implemented to ensure the sidebar header remains fixed at the top of the screen on desktop viewports.