Why Agencies Should Never FTP Plugins: Composer-Managed WordPress with Bedrock
Why enterprise agencies replace manual FTP plugin uploads with Composer-managed Roots Bedrock: 12-factor configuration, immutable lockfiles, and zero-downtime CI/CD.
In agency web development, few practices reveal the gulf between amateur dev shops and elite engineering squads as clearly as how WordPress code is deployed.
In amateur agencies, a familiar, terrifying deployment ritual plays out weekly:
- A developer connects to the live production server over raw FTP or SFTP via FileZilla.
- They upload a modified plugin or theme file directly to
/wp-content/themes/. - Mid-transfer, the connection drops or a syntax error triggers the infamous WordPress “White Screen of Death”.
- Shoppers are locked out of checkout, the client’s marketing director is calling in a panic, and developers spend three frantic hours trying to guess which files were modified.
Even worse, updating plugins via the wp-admin dashboard (Dashboard > Updates > Update All) modifies code directly in production without a Git commit history, ensuring that staging and production environments immediately diverge.
In 2026, professional digital agencies never use FTP or wp-admin plugin updaters. Instead, they engineer WordPress as a modern, 12-factor application using Roots Bedrock and Composer.
Below is our production deployment manual: detailing how to manage WordPress dependencies via Composer, isolate environment configurations, and execute atomic zero-downtime CI/CD deployments.
1. The 12-Factor WordPress Architecture: Roots Bedrock
Standard WordPress mixes core application files, user-uploaded media, configuration settings, and database credentials into a single unstructured web root.
Roots Bedrock re-engineers WordPress around modern software engineering principles:
my-agency-project/
├── .env # Environment secrets (isolated outside web root)
├── composer.json # Declarative PHP dependency manifest
├── composer.lock # Cryptographic lockfile guaranteeing exact parity
├── config/
│ ├── application.php # 12-factor configuration logic
│ └── environments/ # Environment-specific overrides (development, staging)
└── web/ # The public web root (isolated from sensitive files)
├── app/ # Custom content directory (replaces wp-content)
│ ├── mu-plugins/ # Must-use plugins (managed by Composer)
│ ├── plugins/ # Third-party plugins (managed by Composer)
│ ├── themes/ # Custom themes (version controlled)
│ └── uploads/ # User media (symlinked or offloaded to Cloudflare R2)
└── wp/ # WordPress core (managed as Composer dependency)
Key Security & Operational Benefits:
- Isolated Web Root: The web server document root points to
/web/. The.envfile, Git repository, and Composer configs reside outside the web server’s reachable path, completely eliminating the risk of accidental configuration credential leakage. - WordPress Core as a Disposable Dependency: WordPress is not committed to Git; it is a version-pinned dependency in
composer.json("roots/wordpress": "6.7.1"). - Immutable Lockfiles:
composer.lockrecords the exact cryptographic commit hash of every installed plugin, ensuring that staging and production environments run identical code.
2. Managing Premium & Custom Plugins via Composer
A common objection from agency teams is: “How do we manage premium plugins like ACF Pro, Gravity Forms, or WP Rocket that aren’t on packagist.org?”
Composer allows declaring private package repositories and Composer endpoints:
// composer.json
{
"name": "fonda/enterprise-roots-site",
"type": "project",
"repositories": [
{
"type": "composer",
"url": "https://wpackagist.org"
},
{
"type": "composer",
"url": "https://connect.advancedcustomfields.com"
}
],
"require": {
"php": ">=8.2",
"roots/wordpress": "6.7.*",
"roots/wp-config": "1.0.*",
"roots/wp-password-bcrypt": "1.1.*",
"wpackagist-plugin/woocommerce": "9.3.*",
"wpackagist-plugin/redis-cache": "2.5.*",
"advanced-custom-fields/advanced-custom-fields-pro": "^6.3"
},
"config": {
"optimize-autoloader": true,
"preferred-install": "dist",
"allow-plugins": {
"roots/wordpress-core-installer": true,
"composer/installers": true
}
}
}
Updating WooCommerce across local development, staging, and production requires running a single deterministic terminal command:
composer update wpackagist-plugin/woocommerce
git add composer.json composer.lock
git commit -m "chore(deps): update woocommerce to 9.3.2"
git push origin staging
3. Atomic Zero-Downtime Deployment via GitHub Actions
The hallmark of professional agency engineering is Atomic Zero-Downtime Deployment.
When code is deployed, we never overwrite files in place. Instead, we utilize an atomic symlink swap:
/var/www/client-site/
├── current ──▶ /var/www/client-site/releases/202610161400 (Active Symlink)
├── shared/
│ ├── .env
│ └── uploads/ ──▶ (Shared media persistent across all releases)
└── releases/
├── 202610161200 (Previous Release)
└── 202610161400 (New Release — switched in 2ms!)
GitHub Actions Deployment Workflow
# .github/workflows/deploy.yml
name: Deploy Production Bedrock
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup PHP 8.3
uses: shivammathur/setup-php@v2
with:
php-version: '8.3'
- name: Install Composer Dependencies
run: composer install --no-dev --optimize-autoloader --prefer-dist
- name: Build Frontend Assets
run: npm ci && npm run build
- name: Deploy Atomic Release via SSH
uses: deployphp/action@v1
with:
private-key: ${{ secrets.SSH_PRIVATE_KEY }}
dep: deploy production
During deployment:
- The new release is built in an isolated directory.
- Composer dependencies install and Vite compiles Tailwind CSS assets.
- Database migrations execute.
- The web server’s
currentsymlink is atomically swapped to the new release in 2 milliseconds.
If any build step fails, the symlink is never touched. The live production site continues serving customers without a single dropped request.
Automated Post-Deployment Hooks: DB Migrations & Cache Purge
Following the atomic symlink switch, the CI/CD pipeline triggers automated post-deployment hooks:
# Executed automatically inside the /current release directory
wp core update-db # Executes database schema upgrades if required
wp rewrite flush --hard # Regenerates rewrite permalinks
wp redis flush # Purges stale object cache groups in Redis
curl -s -X POST "$MONITORING_HOOK" # Dispatches deployment marker to Sentry & Datadog
4. Telemetry Comparison: Manual FTP vs. Composer Bedrock CI/CD
| Operational Vector | Legacy FTP / wp-admin Workflow | Roots Bedrock + Composer CI/CD |
|---|---|---|
| Deployment Mechanism | Manual FileZilla upload / wp-admin | Automated atomic GitHub Actions |
| Downtime During Deploy | 5 to 25 minutes (Incomplete files) | 0 milliseconds (Atomic symlink) |
| Git Version Control | Untracked plugin updates | 100% auditable Git lockfile history |
| Rollback Capability | Painful 3-hour manual DB restore | Instant 5-second symlink revert |
| Security Posture | Sensitive files exposed in webroot | Credentials isolated outside webroot |
| Developer Onboarding | Days configuring local MySQL dumps | 15 minutes via Docker / Composer |
5. Summary: Elevating WordPress to Enterprise Standards
Treating WordPress as a fragile, FTP-managed hobbyist CMS is an agency operational liability that leads to unbilled emergency fixes, security compromises, and client churn.
By implementing Roots Bedrock and Composer-driven CI/CD:
- You eliminate deployment downtime and broken production updates.
- You maintain 100% version-controlled dependency parity across all environments.
- You provide your agency clients with the security, predictability, and stability of an enterprise 12-factor software application.
To explore related hardened WordPress engineering playbooks across our repository:
- Study our foundational manual Hardened WordPress & High-Scale E-Commerce: Bedrock & Sage.
- Learn high-traffic tuning in Surviving Black Friday on WooCommerce: HPOS & Redis.
- Review visual builder migration in Ditching Elementor & Divi for Roots Sage 10 & ACF Pro.
Ready to modernize your agency’s WordPress deployment pipeline or transition client sites to Roots Bedrock? Contact our engineering team to schedule an infrastructure consultation.
Frequently Asked Questions
Why is managing WordPress plugins via FTP or wp-admin an agency anti-pattern?→
How does Roots Bedrock reorganize WordPress into a 12-factor application?→
How does atomic zero-downtime deployment work with Composer and Bedrock?→
Scaling an agency? Offload your engineering bottlenecks.
Fonda Digital provides senior white-label full-stack development, headless migrations, and hardened WordPress builds under bilateral NDA. Predictable wholesale margins.