Add docker-compose file for development environment #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
robertknight
approved these changes
Jan 23, 2024
Update project dependencies and CI workflow
acelaya
force-pushed
the
local-dev-env
branch
from
0d50eef to
d63c727
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #40
This PR adds a
docker-composeconfig file that will help testing the plugin during development.It includes a WordPress instance, a MySQL database, and mounts the plugin in the proper location.
It currently requires one initial config step in which we set-up the site's admin user, and the plugin needs to be enabled manually. Luckily, this persistes if the container is stopped and started.
In a follow-up PR, I will add a
Makefilethat starts this service withmake servicesand/ormake dev.