gbanyan/digitechflow-wordpress
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: document plugin seeding usage

Browse Source
This commit is contained in:
Gbanyan
2025-11-16 11:18:02 +08:00
parent 30272ecf73
commit 215772b0bc
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@@ -33,6 +33,13 @@ This repository contains a hardened Docker Compose stack for the DigitechFlow Wo
- Local data directories (`db_data/`, `wordpress_data/`, `redis_data/`) plus `wp-config.php` are gitignored to prevent leaking content/secrets. - Local data directories (`db_data/`, `wordpress_data/`, `redis_data/`) plus `wp-config.php` are gitignored to prevent leaking content/secrets.
- `config/plugins.txt` lists plugin slugs to auto-install. Add one per line and rerun `docker compose up wpcli_seed`. - `config/plugins.txt` lists plugin slugs to auto-install. Add one per line and rerun `docker compose up wpcli_seed`.
### Managing the plugin seed list
`config/plugins.txt` is a newline-delimited list of plugin slugs (directory names from wordpress.org). To ensure a plugin is installed and active whenever this stack boots:
1. Add the slug to the file, e.g. `wordpress-seo`.
2. Run `docker compose up wpcli_seed`. The one-shot `wordpress:cli` container will wait for WordPress to be ready, install any missing plugins from the list, and activate them.
3. Repeat whenever you add/remove required plugins. Existing installations are left untouched unless they match entries in the file (in which case they’re only ensured active).
## Operations ## Operations
- Update images: `docker compose pull && docker compose up -d`. - Update images: `docker compose pull && docker compose up -d`.
- View logs: `docker compose logs -f <service>`. - View logs: `docker compose logs -f <service>`.