github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs: clarify why we stop/rebuild apps during upgrade

Browse Source 
[ci skip]
This commit is contained in:
Jose Diaz-Gonzalez
2020-07-14 19:48:10 -04:00
committed by GitHub
parent dea4251b2c
commit 520bc94357
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/getting-started/upgrading.md
View File

@@ -15,7 +15,6 @@ Your operating system may occasionally provide security updates. We recommend se
Docker releases updates periodically to their engine. We recommend reading their release notes and upgrading accordingly. Please see the [Docker documentation](https://docs.docker.com/) for more details. Docker releases updates periodically to their engine. We recommend reading their release notes and upgrading accordingly. Please see the [Docker documentation](https://docs.docker.com/) for more details.
## Migration Guides ## Migration Guides
Before upgrading, check the migration guides to get comfortable with new features and prepare your deployment to be upgraded. Before upgrading, check the migration guides to get comfortable with new features and prepare your deployment to be upgraded.
@@ -29,11 +28,18 @@ Before upgrading, check the migration guides to get comfortable with new feature
- [Upgrading to 0.6](/docs/appendices/0.6.0-migration-guide.md) - [Upgrading to 0.6](/docs/appendices/0.6.0-migration-guide.md)
- [Upgrading to 0.5](/docs/appendices/0.5.0-migration-guide.md) - [Upgrading to 0.5](/docs/appendices/0.5.0-migration-guide.md)
## Before upgrading ## Before upgrading
If you'll be updating docker simultaneously, it's recommended that you stop all If you'll be updating docker or the herokuish package simultaneously, it's recommended
applications before upgrading: that you stop all applications before upgrading and rebuild afterwards. This is not
required if the upgrade only impacts the `dokku` package.
Why do we recommend stopping all apps?
- `docker`: Containers may be randomly reset during the upgrade process, resulting in
requests being sent to the wrong containers. Acknowledging and scheduling downtime
thus becomes much more important.
- `herokuish`: While not required, it may be useful to take advantage of the
```shell ```shell
# for 0.11.4 and newer versions, use: # for 0.11.4 and newer versions, use:
@@ -65,7 +71,6 @@ dokku ps:rebuildall
> Please see the [images documentation](/docs/deployment/methods/images.md) and [tar documentation](/docs/deployment/methods/tar.md) > Please see the [images documentation](/docs/deployment/methods/images.md) and [tar documentation](/docs/deployment/methods/tar.md)
> for instructions on rebuilding applications deployed by those plugins. > for instructions on rebuilding applications deployed by those plugins.
## Upgrading using `dokku-update` ## Upgrading using `dokku-update`
We provide a helpful binary called `dokku-update`. This is a recommended package that: We provide a helpful binary called `dokku-update`. This is a recommended package that:
@@ -76,7 +81,6 @@ We provide a helpful binary called `dokku-update`. This is a recommended package
When installing from source, this is available from `contrib/dokku-update`, and is also available on Debian and RPM-based systems from our package repositories under the name `dokku-update`. When installing from source, this is available from `contrib/dokku-update`, and is also available on Debian and RPM-based systems from our package repositories under the name `dokku-update`.
## Upgrading using `apt` ## Upgrading using `apt`
If Dokku was installed in a Debian or Ubuntu system, via `apt install dokku` or `bootstrap.sh`, you can upgrade with `apt`: If Dokku was installed in a Debian or Ubuntu system, via `apt install dokku` or `bootstrap.sh`, you can upgrade with `apt`: