Forging Forge

on YouTube ↗35m

" summary

Forge gets rebuilt from the ground up: a new back end with organizations and teams and RBAC, pagination and search for accounts with hundreds of servers, and an action-based refactor to replace monolithic repositories. The rollout uses feature-flagging the entire app (including an Always Driver) and entitlements for flexible plan limits. Operational wins include Laravel VPS with DigitalOcean to cut provisioning from minutes toward instant, plus zero‑downtime deploys, heartbeats, server metrics and a new API.

AI-written summary · about

" chapters (19)

1. 0:00Start
2. 1:34High level overview of what Forge is and its origins in 2014
3. 2:05How Forge influenced Laravel’s growth
4. 3:30Evolution of Forge and the increasing complexity created by 10 years of features and decisions
5. 4:20Circles, shared access and why the legacy permission model became confusing and limiting
6. 5:38How the Accel investment enabled resourcing for Cloud, Nightwatch and a dedicated Forge team
7. 6:02Differences between Laravel Forge and Laravel Cloud, clarifying their respective roles
8. 7:39Why the old Forge UI and architecture had hit their limits and could not support future growth
9. 8:09Technical debt, legacy code and how you can see the evolution of Laravel reflected in Forge
10. 9:03UX limitations, navigation sprawl and the need for a more coherent interface
11. 10:00Architecture redesign, including rewriting the back end to support organisations and pagination
12. 12:00How the team approached shipping a completely new backend without breaking existing production users
13. 17:27Large customers with hundreds of servers made pagination, search and better routing essential
14. 20:00Rewriting Forge instead of versioning it, and how they maintained compatibility
15. 26:41Rapid hiring, cross training engineers and preparing the team for the redesigned Forge architecture
16. 27:07Laravel VPS idea as a way to dramatically improve onboarding friction and provisioning speed
17. 27:41Server provisioning pain points, slow MySQL install and how they initially shaved minutes off
18. 28:36Taylor’s “two minutes or bust”
19. 32:46Foundational improvements position Forge for another decade of growth

" related talks

• 28mCultivating success with LaravelRichard Merryweather · Laracon AU 2023
• 44mBuilding a complex product while scaling a team and a business on LaravelAlex Lüneburg, Richard Wyke · Laracon AU 2018
• 26mJames Brooks :: Working at LaravelJames Brooks · Laracon EU 2024
• 29mWe Have Always Done It This Way! Now Let’s Try Something Completely DifferentEliran Bivas · GitOpsCon Europe 2022
• 30mFord Motor Company’s Transition from Auto-Motive to Auto-MobilityMohsin Yusuf Ahmed, Manu Pasari · Cloud Foundry Summit Silicon Valley 2017
• 35mFire It Up: How Empowered People Automated Provisioning In 6 Datacenters Across 4 ContinentsJosh sheram · Big Ruby 2013
• 17mDeployments We Can Believe InDiego Lapiduz · Cloud Foundry Summit 2015
• 16mDeployments We Can Believe InDiego Lapiduz · Cloud Foundry Summit 2015