Devops @ Princeton: How we track, maintain, and deploy hundreds of sites
summary
Princeton runs a custom Symfony application that inventories and provisions sites into Acquia, stores off‑site backups with a restoreable console command, and collects nightly stats for about 280 Drupal-template sites (plus ~40 custom D7 sites and ~25 legacy Roxen sites; ~400 total campus sites). Deployments use Deployer, Bitbucket + Bitbucket Pipelines, Probo, and New Relic; visual checks use BackstopJS and regression catching relies on Behat automated tests (slow but effective) within a monthly release cycle.
AI-written summary · about
chapters (9)
- 0:00Web Development Services
- 17:39Local Dev Environment
- 20:14Code workflow • New branch for each feature/bus
- 21:42Testing Features & Fixes
- 22:42Deploy to Dev Bitbucket pipeline manually triggered 1. Checkout "develop" branch 2. Rum grunt to create build artifact 3. Clone Acqua repo and checkout develop branch 4. Sync build artifact to Acquia repa, commit and push
- 25:36Deploy to Test 1. Another Bitbucket pipeline 2. Merge develop' branch into 'stage branch 2. Acquia cloud hook runs
- 29:20Deploy to Prod 1. Another Bitbucket pipeline 2. Merge "stage branch into master" branch 3. Push to Acqua 2. Acquia cloud hook runs 3. Monitor New Relie 4. Notify customers Website Wednesday
- 30:33Drupal 7 Custom Platform
- 49:05Questions?
related talks
01h 08mPrinceton Site Builder: Behind the Scenes
56mDigital transformation at Argonne National Laboratory
20mCERN's 1500 Drupal Websites on Kubernetes: Sa...
46m10+ Deploys Pe
38mWhat's Really to Blame?
46mDevops for PHP Developers
40mThe Butler Did It: Putting Jenkins To Work For You
59mDevOps for the Discouraged