这是indexloc提供的服务，不要输入任何密码
Skip to content

Clarify upgrading documentation #2039

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 29, 2016
Merged

Clarify upgrading documentation #2039

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/upgrading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,10 @@ Migration guides contain information regarding the new features introduced in ea

## General Information

Upgrading is not advised on running apps. Stop them before with `dokku ps:stop <app>`.
Copy link
Member

@josegonzalez josegonzalez Mar 29, 2016

Choose a reason for hiding this comment

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

Is this true, @michaelshobbs ?

Copy link
Member

@michaelshobbs michaelshobbs Mar 29, 2016

Choose a reason for hiding this comment

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

I would think so. I wouldn't upgrade on a running "production" host. Specifically when we require a particular version of docker that could potentially cause that package to be upgraded would cause the docker daemon to restart. Thus, resulting in downtime.

Copy link
Member

@michaelshobbs michaelshobbs Jul 26, 2016

Choose a reason for hiding this comment

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

It should be noted that docker >=1.11 promises your containers don't need to be restarted if the docker daemon is restarted. However live upgrades in a production level environment (without fail overs) are not recommended.


Before using `apt-get install`, run `apt-get update` to download the latest packages.

If dokku was installed via a debian package, you can upgrade dokku via the following command:

```shell
Expand All @@ -37,7 +41,7 @@ sudo DOKKU_BRANCH=master make install
sudo make install
```

All changes will take effect upon next application deployment. To trigger a rebuild of every application, simply run the following command:
All changes will take effect upon next application deployment. To trigger a rebuild and restart every application, simply run the following command:

```shell
dokku ps:rebuildall
Expand Down