This document provides a comprehensive overview of our infrastructure setup, focusing on our AWS organization structure, account management, and access procedures.

We use AWS ElastiCache for Valkey as our primary caching solution across all environments. Valkey is an open-source, Redis-compatible in-memory data store that provides high performance and reliability for our applications.

What

Mapping GitLab CI concepts and patterns to GitHub Actions equivalents. Use alongside gh actions-importer for automated translation, then review and adjust using this reference.

Why we cache bots

This setup grants read-only access to farfalla's HTTP access log (and any other Lambda log group) from a local AWS CLI without storing long-lived production credentials. The path is cross-account sts an IAM user in the publica.la account assumes a scoped read-only role that lives in the production account.

These queries were used to produce the data in trafficreport.md.

How to replicate GitLab's when: manual deploy behavior in GitHub Actions using environment protection rules. This pattern gives developers an approval button visible in the PR checks, similar to GitLab's inline manual deploy button.

Introduction

Every uses: entry in every GitHub Actions workflow across the publicala organization must be pinned to a specific version. This policy defines how to pin, what to pin to, and how to handle future deprecations without accumulating backlogs.

Introduction

We are migrating all source code repositories from GitLab (publicala group) to GitHub (publicala org, Enterprise plan). This document covers motivation, scope, approach, and current state.

Laravel Cloud is our deployment platform, replacing Laravel Vapor for hosting Laravel services. Not all projects are on Cloud yet - we're migrating incrementally.

Performance comparison between Laravel Vapor and Laravel Cloud.

Repositories that follow the feature/ → dev → main workflow enforce merge commit only* when a PR is merged into main. Squash and rebase merges are disabled for that target.

Step-by-step checklist for migrating repositories from GitLab to GitHub. Each repo follows the same per-repo process; cross-cutting tasks are handled once after all repos are moved.

This document captures exploration into alternatives to SingleStore Helios for our backing database. It is not a committed migration plan. Treat it as a workload analysis, a survey of candidate platforms, and a list of open questions to inform a future decision.

Overview

This document describes how the Zoo environment is configured to support Playwright testing across multiple domains, specifically for use by both Volpe and Criceto projects.

Catalog of 34 active GitLab repositories in the publicala group, organized by migration priority. Archived repos (76) are excluded; GitLab remains as reference for those. Data sourced from GitLab API and local repository inspection.

We use Cloud Runner for our GitLab CI/CD runners. They provide fully managed runners so we don't have to maintain our own infrastructure.

Cloudflare Worker that sits between repository Slack integrations and Slack itself, filtering out bot noise before forwarding. Currently wired to GitLab's group-level Slack integration; GitHub support is planned.

Summary of data shared with Ryan (Google Doc). This doc is the engineering reference.

Step-by-step guide for migrating Laravel projects from Vapor to Cloud. For Cloud-specific configuration patterns and known gotchas, see the Configuration Reference in the Laravel Cloud overview.