Updated README to include necessary information when running multiple isolated devstacks for same host. - #569
Conversation
|
Thanks for the pull request, @ztraboo! I've created OSPR-4866 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
|
Ready for edX review. |
693e9c8 to
574d744
Compare
|
FYI I'll be away from keyboard until Aug. 3rd, so I won't be able to revert my review until then. |
02985eb to
b3d3fd3
Compare
|
@regisb I made your recommended changes above. Please review https://github.com/CUCWD/devstack/blob/ztraboo/multiple-releases-one-machine-u1/README.rst#how-do-i-run-multiple-named-open-edx-releases-on-same-machine when you can. Thanks. |
b3d3fd3 to
f5a74ca
Compare
|
@regisb I made those changes here https://github.com/CUCWD/devstack/tree/ztraboo/multiple-releases-one-machine-u1#how-do-i-run-multiple-named-open-edx-releases-on-same-machine. Please review when you have time. |
|
@nedbat This is ready, do you have some time to review it? |
92966f0 to
c96d65e
Compare
regisb
left a comment
There was a problem hiding this comment.
A few additional minor changes are required. We're almost there!
c96d65e to
b4e7ff0
Compare
|
@regisb Sorry I was out last week. Please review changes with edx/devstack@c0b482d and let me know if you need me to revise anything. |
b4e7ff0 to
c0b482d
Compare
|
@regisb Thanks for reviewing this. CC @kdmccormick @jmbowman |
regisb
left a comment
There was a problem hiding this comment.
Please make sure all outstanding conversations can be resolved.
…le isolated devstacks for same host. This is the documentation needed for https://github.com/edx/devstack/pull/532 @kdmccormick, @jmbowman, @arbrandes, @regisb
c0b482d to
52c629e
Compare
|
@regisb Once we get this readme resolved I'll apply those changes to https://github.com/edx/devstack/pull/564 too. Thanks for the review. |
…nging releases. - These were additional review changes requested by @regisb.
52c629e to
2c799a0
Compare
…or the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…or the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…or the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…or the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
- Fixing review from @regisb
89ff8de to
149bc79
Compare
|
@ztraboo 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
|
Thanks for your patience and cooperation @ztraboo! |
|
No problem @regisb. I appreciate a thorough review. Helps me code better. :) |
…s one machine (regisb review). Comments came from `master` edx/devstack@c0b482d Fix issue with `docker-compose config` not outputting configuration information when `$(DOCKER_COMPOSE_FILES)` was excluded from the command. It appears that leaving out `$(DOCKER_COMPOSE_FILES)` caused the `docker-compose config` to not include the **volume** information for services within the `docker-compose.yml` file, as well as, excluding additional services like `docker-compose-{analytics-pipeline,watchers}.yml` to name a few. Update provision-ecommerce.sh with recommended changes from @morenol Co-authored-by: morenol <13-10934@usb.ve> Merging additional updates based on openedx-unsupported#569 changes for the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…s one machine (regisb review). Comments came from `master` edx/devstack@c0b482d Fix issue with `docker-compose config` not outputting configuration information when `$(DOCKER_COMPOSE_FILES)` was excluded from the command. It appears that leaving out `$(DOCKER_COMPOSE_FILES)` caused the `docker-compose config` to not include the **volume** information for services within the `docker-compose.yml` file, as well as, excluding additional services like `docker-compose-{analytics-pipeline,watchers}.yml` to name a few. Update provision-ecommerce.sh with recommended changes from @morenol Co-authored-by: morenol <13-10934@usb.ve> Merging additional updates based on #569 changes for the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…s one machine (regisb review). Comments came from `master` edx/devstack@c0b482d Fix issue with `docker-compose config` not outputting configuration information when `$(DOCKER_COMPOSE_FILES)` was excluded from the command. It appears that leaving out `$(DOCKER_COMPOSE_FILES)` caused the `docker-compose config` to not include the **volume** information for services within the `docker-compose.yml` file, as well as, excluding additional services like `docker-compose-{analytics-pipeline,watchers}.yml` to name a few. Update provision-ecommerce.sh with recommended changes from @morenol Co-authored-by: morenol <13-10934@usb.ve> Merging additional updates based on openedx-unsupported#569 changes for the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
…s one machine (regisb review). Comments came from `master` edx/devstack@c0b482d Fix issue with `docker-compose config` not outputting configuration information when `$(DOCKER_COMPOSE_FILES)` was excluded from the command. It appears that leaving out `$(DOCKER_COMPOSE_FILES)` caused the `docker-compose config` to not include the **volume** information for services within the `docker-compose.yml` file, as well as, excluding additional services like `docker-compose-{analytics-pipeline,watchers}.yml` to name a few. Update provision-ecommerce.sh with recommended changes from @morenol Co-authored-by: morenol <13-10934@usb.ve> Merging additional updates based on openedx-unsupported#569 changes for the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
This is the documentation needed for https://github.com/edx/devstack/pull/532
@kdmccormick, @jmbowman, @arbrandes, @regisb
.