elome-com-bedrock¶
A modular Bedrock WordPress site managed via Composer, running in Docker locally and deployed via GitHub Actions to production.
Overview¶
| Item | Value |
|---|---|
| Repo | subscribed-aps/elome-com-bedrock |
| PHP | >= 7.4 |
| WordPress | ~6.8 |
| WooCommerce | ~10.x |
| Packagist | packagist.subscribed.build |
| Local stack | Docker (PHP-FPM, MariaDB, Nginx, Redis) |
| Deployment | GitHub Actions → subscribed-aps/workflows |
| Error tracking | Sentry |
| Environment vars | Dotenv Vault |
Documentation¶
- Local Setup — Get the project running on your machine
- Architecture — Stack, folder structure, and key concepts
- Deployment — How deploys work and how to trigger them
- Plugins & Packages — Custom and premium plugins managed via Composer
Key Concepts¶
Bedrock changes the standard WordPress layout: WordPress core lives in web/wp/, the content directory is web/app/ (instead of wp-content/), and all plugins/themes are managed via Composer.
Dotenv Vault is used to manage environment variables across environments. The .env.vault file is committed to the repo; the DOTENV_KEY is stored as a secret and injected at runtime to decrypt the correct environment.
Custom Packagist — Private packages (prefixed barberklingen/, barberklingen-premium/, subscribed/) are pulled from packagist.subscribed.build. You need SSH access configured to authenticate.