Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Expand docker-compose.yml file to include wpcli functionality #200

Closed
1 of 6 tasks
possumbilities opened this issue Jul 19, 2022 · 1 comment · Fixed by #225
Closed
1 of 6 tasks

[Feature] Expand docker-compose.yml file to include wpcli functionality #200

possumbilities opened this issue Jul 19, 2022 · 1 comment · Fixed by #225
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Milestone

Comments

@possumbilities
Copy link
Contributor

possumbilities commented Jul 19, 2022

Problem

See #199, this builds from there.

MVP
At a minimum:

 - setup MySQL server (MariaDB preferably)
 - setup a web server (Apache), running latest WordPress files
 - make Web and DB server connect with each other appropriately
 - mount the db locally, so it persists
 - mount the WordPress install locally, so it persists
 - mount the wp-plugin-creativecommons plugin directory into the web server at wp-content/plugins/, so it can be user activated
-  include appropriate .gitignore additions so local mount points are not tracked ( ./dev/db & ./dev/wordpress)
 update documentation to reflect new docker compose one-liner referencing docker-compose.yml file

The baseline Docker Image would benefit from having the fully featured functionality of the WP CLI command line utility bundled in.

Description

Once #199 is implemented, then as an expansion, WP CLI should be included in the docker-compose.yml file to allow more robust automated WP configuration and testing. At a minimum it can be included for devs to use as needed, but alternatively this opens the possibilities for later functionality to be baked in that would perform automated full WordPress installations or configuration patterns.

MVP

  • setup WP CLI img in docker-compose.yml file
  • link to web server and db
  • update any relevant documentation for use of wp cli in this context

Alternatives

There are currently no known alternatives to WP CLI that I am aware of.

Additional context

Will pull an image from the official WP CLI image variant found here: https://hub.docker.com/_/wordpress

Decisions left to to make

  • should there be any options exposed to aide in automatic installation setup by default? (single site, network, etc.)?
  • If so, is there valid reason to automatically activate the wp-plugin-creativecommons plugin? (speeds up dev testing, BUT downside is that it leaves off the potential to test GUI based activation in WP version upgrades.

Implementation

  • I would be interested in implementing this feature.
@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Jul 19, 2022
@possumbilities possumbilities self-assigned this Jul 19, 2022
@possumbilities possumbilities added this to the Backlog milestone Jul 19, 2022
@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Jul 19, 2022
@ArchanRD ArchanRD mentioned this issue Mar 9, 2024
7 tasks
@ArchanRD
Copy link
Contributor

ArchanRD commented Mar 9, 2024

@TimidRobot @possumbilities I've created a PR for this issue. Please check it out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants