-
Notifications
You must be signed in to change notification settings - Fork 17
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
refactor(dev-env): let dev-tools
handle their volumes
#2139
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
03ff85d
to
5830fcf
Compare
@@ -31,6 +30,7 @@ services: | |||
devtools: {} | |||
scripts: | |||
initOnly: true | |||
entrypoint: sh -c 'test -d /dev-tools-orig && /usr/bin/rsync -a --delete /dev-tools-orig/ /dev-tools/ || true' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backward compatibility :-(
dev-tools
handle their volumedev-tools
handle their volumes
I've tested both for a) existing environment and b) fresh env under Mac OS X
Manual start of nginx container after that works. |
Updated service dependencies. |
e36383f
to
6d13d47
Compare
6d13d47
to
f77bded
Compare
Quality Gate passedIssues Measures |
Tested, works! |
Description
This PR updates the dev-env code to avoid messing with the
dev-tools
volume.dev-tools
volumes;php
service starts afterdevtools
completes to avoid race conditions;/dev-tools-orig
with/dev-tools
. This step is necessary because Lando sets its own entrypoint script if we don't provide ours.Related PR: Automattic/vip-container-images#985 (must be merged before this one)
Volume removal logic was introduced in #1317.
Pull request checklist
New release checklist
Steps to Test
/devtools
vip-container-images#985,cd dev-tools && docker build -t dev-tools:local
npm run build && npm link
~/.local/share/vip/dev-environment/vip-local/.lando.local.yml
:vip dev-env start
and ensure everything worksvip dev-env shell -- sh -c 'md5sum /dev-tools/*'
and save the output.docker build -t dev-tools:local
)vip dev-env start
).vip dev-env shell -- sh -c 'md5sum /dev-tools/*'
and compare the output with the one from step 6. The hash for the updated script must differ.