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

Update of upgrade-documentation #790

Merged
merged 1 commit into from
Jun 13, 2020
Merged

Update of upgrade-documentation #790

merged 1 commit into from
Jun 13, 2020

Conversation

roadrash2108
Copy link
Contributor

added "docker-compose up -d" as default for bringing containers up after upgrade (to match the description of installation-documentation).

"docker-compose up -d" als Default hinzugefügt.
Copy link
Collaborator

@adriankumpf adriankumpf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@adriankumpf adriankumpf merged commit 6d93b28 into teslamate-org:master Jun 13, 2020
@roadrash2108 roadrash2108 deleted the patch-1 branch June 15, 2020 08:46
@cwanja
Copy link
Collaborator

cwanja commented Oct 6, 2020

Is there any benefit to doing a docker system prune during an upgrade? For example, here is my upgrade script:
docker-compose down && docker-compose pull && docker system prune && docker-compose up -d. Sorry for the newbie docker questions 😊

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