Overview

Recent development activity focused on code style consistency and updates to the database schema.

Code Formatting

Applied automated formatting fixes using php-cs-fixer. This ensures consistent code style across the project, improving readability and maintainability. The tool automatically adjusts spacing, indentation, and other stylistic elements according to predefined rules.

Introduction

The application's dashboard was experiencing crashes for tenants that had not yet run the commits migration. This post details the solution implemented to gracefully handle the absence of the commits table in the tenant schema, preventing dashboard failures.

The Problem

When the dashboard attempted to query the commits table to display user activity and calculate API

Overview

This update focuses on improving the user experience within the Filament admin panel by reorganizing the navigation structure. Specifically, resources related to support and feedback have been relocated to a dedicated 'Support' navigation group.

Motivation

The primary goal is to declutter the 'System' navigation group. By moving support-related resources to their own group, the

Introduction

After consolidating billing to a tenant-based system (Phase 3), we encountered an issue with the Cashier package. The default customer model was still set to User, causing errors when Stripe webhook events triggered.

The Problem

The stripe_id column, expected by Cashier, was not found because it was looking in the User model instead of the Tenant model.

Introduction

We've given the Devlog.ist landing page a fresh coat of paint, embracing a retro brutalist aesthetic. This update focuses on improving the user experience through visual design and unified messaging across languages.

Design Overhaul

The redesign touches several key areas:

• Welcome Page: Incorporating thick borders, hard offset shadows, and geometric grid backgrounds

Introduction

In multi-tenant applications, maintaining database schema consistency across all tenants can be challenging, especially during phased rollouts or migrations. This post addresses a common issue: handling older tenant schemas that may lack certain tables.

The Challenge

Older tenant schemas may not have all the tables required by newer application versions.

Introduction

The EcoRuta form, used for managing certified recycling routes, has undergone a significant redesign. This update focuses on modernizing the user interface, improving the user experience, and adding dark mode support to align with the Landing module's design patterns.

Key Changes

The redesign includes several key improvements:

• Layout Update: The form now utilizes

Introduction

Recent development efforts have focused on refining the Batteries platform, addressing review comments, and improving code quality across several modules.

Key Updates

Several key areas have been addressed:

• Data Handling: Improved data cleaning within DataCleanerService by adding a null check before encoding validation to prevent errors with null values.

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

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.