A work-in-progress starter for a headless implementation of WordPress. There are a lot of dependencies to do something like this (e.g., PhpMyAdmin, MySQL, WordPress, Express, etc.), so a Docker container seems like a good way of going about it. Data persistence and migration may be an issue, however.
This is a reverse engineering of headless-wp-starter.
- Create a new image based off the WordPress image to automate the installation and activation of themes and plugins. Will probably need to use WP CLI.
- Figure out a good way to back up the database if the volumes are deleted.
- Create an environment variable file in root directory:
MYSQL_ROOT_PASSWORD=
MYSQL_DATABASE=
MYSQL_USER=
MYSQL_PASSWORD=
WORDPRESS_DB_USER=
WORDPRESS_DB_PASSWORD=
In the above, MYSQL_USER and WORDPRESS_DB_USER must be the same and MYSQL_PASSWORD and WORDPRESS_DB_PASSWORD must be the same.
- Start the services in detached mode:
docker-compose up -d
- Stop the services:
docker-compose down
If you want to delete the persisted data from the db_data volume, optionally add the --volumes flag:
docker-compose down --volumes