Skip to content
This repository was archived by the owner on Jan 17, 2025. It is now read-only.

Commit 541e2ad

Browse files
author
Sara Lovell
committed
expand docker usage instructions to outline what occurs on build, and how to proceed with initial wp install
1 parent 6c790c6 commit 541e2ad

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,17 @@ OR
128128

129129
`docker compose -f ./dev/docker-compose.yml down` to stop containers
130130

131+
The first time the build process is run via `docker compose -f ./dev/docker-compose.yml up`, docker will create two directories within your local repository clone:
132+
133+
- `./dev/db` where the database and relevant config will be stored
134+
- `./dev/wordpress` where the WordPress files will be stored
135+
136+
It will then mount this plugin's root directory into the `/wp-content/plugins/` directory of the WordPress installation. Edits made to your local plugin clone will reflect within the build.
137+
138+
You can then navigate to `http://localhost:8080/` and proceed with a manual WordPress installation. After the initial installation the WordPress install will persisist between docker sessions.
139+
140+
If you need to reset the WordPress install to a "clean slate" you can simply delete the `db` and `wordpress` directories respectively, and then run `docker compose -f ./dev/docker-compose.yml up` again to initializw a clean install build.
141+
131142

132143
## Release Schedule
133144

0 commit comments

Comments
 (0)