Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@aldeed
Copy link
Contributor

@aldeed aldeed commented Jan 2, 2020

Impact: minor
Type: chore

Changes

When you clone this branch and run docker-compose up, it will now pull and use the latest published reactioncommerce/reaction:release-3.0.0 image from DockerHub instead of node-dev. Host files are not linked in and NPM deps are not reinstalled.

Breaking changes

Breaking only for devs who will now need to run ln -s docker-compose.dev.yml docker-compose.override.yml to get the previous behavior.

Testing

  • Verify dc up starts from the published image.
  • After dc down, run ln -s docker-compose.dev.yml docker-compose.override.yml and then dc up again. Verify it now uses local files and reloads when you change files.
  • After dc down, run rm docker-compose.override.yml to remove the override file. It should be back to running in prod mode when you do dc up.

@aldeed aldeed requested a review from focusaurus January 2, 2020 03:31
@aldeed aldeed merged commit f3ae988 into release-3.0.0 Jan 2, 2020
@aldeed aldeed deleted the chore-use-published-image-for-dc branch January 2, 2020 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants