Skip to content
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

Merged
merged 8 commits into from
Sep 27, 2022
Merged

ISSUE-63: Upgrade from RC3 to 1.0.0 doc needs edits #70

merged 8 commits into from
Sep 27, 2022

Conversation

aksm
Copy link
Contributor

@aksm aksm commented Sep 6, 2022

Resolves part of #63

Copy link
Member

@DiegoPino DiegoPino left a 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:
Copy link
Member

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

Copy link
Contributor Author

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

@@ -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.
Copy link
Member

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

Copy link
Contributor Author

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

@DiegoPino DiegoPino merged commit 7f5e01d into esmero:1.0.0 Sep 27, 2022
@aksm aksm deleted the ISSUE-63 branch October 20, 2022 15:28
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.

2 participants