-
Notifications
You must be signed in to change notification settings - Fork 13
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
ISSUE-63: Upgrade from RC3 to 1.0.0 doc needs edits #70
Conversation
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.
Some changes are needed. Check slack for what happened to our friends at WWU last week
```shell | ||
cp docker-compose-osx.yml docker-compose.yml | ||
``` | ||
Then copy the appropriate `docker-compose` file for your architecture: |
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.
@aksm a step is missing here. The user should always backup the original docker-compose.yml. Most of our users end customizing/adding/removing configs and when doing the copy they overwrite all their particularities. Also a git diff example would be great
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.
Ok, does this look ok? 247c2be
docs/upgradeFromRC3.md
Outdated
@@ -217,6 +210,7 @@ Important here is the `STATUS` column. It **needs** to be a number that goes up | |||
### Step 3: | |||
|
|||
Instead of using the provided `composer.lock` out of the box we are going to loosen certain dependencies and bring manually Archipelago modules, all this to make update easier and future upgrades less of a pain. |
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.
We provide now a composer.lock.default. We also need to be sure that the user doing this runs all composer require against the original (their) composer.lock and not against the new default one
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.
And does this make sense? 8a7361c
Resolves part of #63