docs/getting-started/upgrading.md

# Upgrading

If your version of Dokku is pre 0.3.0 (check with `dokku version`), we recommend [a fresh install](/dokku/getting-started/installation/) on a new server.

## Migration Guides

Before upgrading, check the migration guides to get comfortable with new features and prepare your deployment to be upgraded.

### 0.5 Migration Guide

- [0.5 Migration Guide](/dokku/appendices/0.5.0-migration-guide/)

### 0.6 Migration Guide

- [0.6 Migration Guide](/dokku/appendices/0.6.0-migration-guide/)

### 0.7 Migration Guide

- [0.7 Migration Guide](/dokku/appendices/0.7.0-migration-guide/)

## Upgrade Instructions

If Dokku was installed via `apt-get install dokku` or `bootstrap.sh` (most common), upgrade with:

```shell
sudo apt-get update
dokku apps
dokku ps:stop APP # repeat to shut down each running app
sudo apt-get install -qq -y dokku herokuish sshcommand plugn
dokku ps:rebuildall # rebuilds all applications
```

> If you have any applications deployed via the `tags` or `tar` commands, do not run the `ps:rebuildall` command,
> and instead trigger `ps:rebuild` manually for each `git`-deployed application:
>
> ```
> dokku ps:rebuild APP
> ```
>
> Please see the [images documentation](/dokku/deployment/methods/images/) and [tar documentation](/dokku/deployment/methods/tar/)
> for instructions on rebuilding applications deployed by those plugins.

### Upgrade From Source

If you installed Dokku from source (less common), upgrade with:

```shell
dokku apps
dokku ps:stop APP # repeat to shut down each running app
cd ~/dokku
git pull --tags origin master

# continue to install from source
sudo DOKKU_BRANCH=master make install

# upgrade to debian package-based installation
sudo make install
dokku ps:rebuildall # rebuilds all applications
```

To upgrade herokuish from source, upgrade with:

```shell
cd /tmp
git clone https://github.com/gliderlabs/herokuish.git
cd herokuish
git pull origin master
IMAGE_NAME=gliderlabs/herokuish BUILD_TAG=latest VERSION=master make -e build-in-docker
```
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00			`# Upgrading`

Use correct casing for Dokku name lowercase should only be used to refer to the binary, not the project 2016-09-03 04:39:12 -04:00			If your version of Dokku is pre 0.3.0 (check with `dokku version`), we recommend [a fresh install](/dokku/getting-started/installation/) on a new server.
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
Fix formatting on upgrading docs [ci skip] 2016-03-21 01:41:03 -04:00			`## Migration Guides`
Add link to 0.5.x migration guide [ci skip] 2016-03-02 23:10:05 -05:00
condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`Before upgrading, check the migration guides to get comfortable with new features and prepare your deployment to be upgraded.`
Add link to 0.5.x migration guide [ci skip] 2016-03-02 23:10:05 -05:00
Add a migration guide for 0.7.0 [ci skip] 2016-08-26 14:11:56 -04:00			`### 0.5 Migration Guide`

/docs => /dokku in upgrading.md 2016-04-20 15:43:39 -05:00			`- [0.5 Migration Guide](/dokku/appendices/0.5.0-migration-guide/)`
Add a migration guide for 0.7.0 [ci skip] 2016-08-26 14:11:56 -04:00
			`### 0.6 Migration Guide`

allow zero-downtime to be completely disabled. closes #2073. closes #2125 2016-05-09 16:03:07 -07:00			`- [0.6 Migration Guide](/dokku/appendices/0.6.0-migration-guide/)`
Add a migration guide for 0.7.0 [ci skip] 2016-08-26 14:11:56 -04:00
			`### 0.7 Migration Guide`

Fix link [ci skip] 2016-08-26 14:19:55 -04:00			`- [0.7 Migration Guide](/dokku/appendices/0.7.0-migration-guide/)`
Update upgrading.md 2016-03-28 21:09:37 -05:00
condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`## Upgrade Instructions`
Update upgrading.md 2016-03-28 21:09:37 -05:00
Use correct casing for Dokku name lowercase should only be used to refer to the binary, not the project 2016-09-03 04:39:12 -04:00			If Dokku was installed via `apt-get install dokku` or `bootstrap.sh` (most common), upgrade with:
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
Use shell keyword for codeblock guard 2014-12-19 15:09:38 -05:00			```shell
condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`sudo apt-get update`
			`dokku apps`
docs: standardize on node-js-app as the app name We’ll probably want to update this to whatever the hip language of the day is, but for now, having the same reference everywhere works. 2016-11-20 15:37:05 -07:00			`dokku ps:stop APP # repeat to shut down each running app`
docs: upgrade sshcommand and plugn as well [ci skip] 2016-11-27 19:55:02 -07:00			`sudo apt-get install -qq -y dokku herokuish sshcommand plugn`
Document caveats around ps:rebuild and tags/tar deployed applications. Closes #2374 The tags and tar plugins do not necessarily build from source, and running `ps:rebuild` can have some unexpected output in certain cases. Rather than try to handle that complexity - it's a lot - documenting the edge cases is the most appropriate way forward. 2016-09-06 20:26:53 -04:00			`dokku ps:rebuildall # rebuilds all applications`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00			```

Document caveats around ps:rebuild and tags/tar deployed applications. Closes #2374 The tags and tar plugins do not necessarily build from source, and running `ps:rebuild` can have some unexpected output in certain cases. Rather than try to handle that complexity - it's a lot - documenting the edge cases is the most appropriate way forward. 2016-09-06 20:26:53 -04:00			> If you have any applications deployed via the `tags` or `tar` commands, do not run the `ps:rebuildall` command,
			> and instead trigger `ps:rebuild` manually for each `git`-deployed application:
			`>`
			> ```
			`> dokku ps:rebuild APP`
			> ```
			`>`
			`> Please see the [images documentation](/dokku/deployment/methods/images/) and [tar documentation](/dokku/deployment/methods/tar/)`
			`> for instructions on rebuilding applications deployed by those plugins.`

condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`### Upgrade From Source`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
Use correct casing for Dokku name lowercase should only be used to refer to the binary, not the project 2016-09-03 04:39:12 -04:00			`If you installed Dokku from source (less common), upgrade with:`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			```shell
condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`dokku apps`
docs: standardize on node-js-app as the app name We’ll probably want to update this to whatever the hip language of the day is, but for now, having the same reference everywhere works. 2016-11-20 15:37:05 -07:00			`dokku ps:stop APP # repeat to shut down each running app`
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			`cd ~/dokku`
			`git pull --tags origin master`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			`# continue to install from source`
			`sudo DOKKU_BRANCH=master make install`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			`# upgrade to debian package-based installation`
			`sudo make install`
Document caveats around ps:rebuild and tags/tar deployed applications. Closes #2374 The tags and tar plugins do not necessarily build from source, and running `ps:rebuild` can have some unexpected output in certain cases. Rather than try to handle that complexity - it's a lot - documenting the edge cases is the most appropriate way forward. 2016-09-06 20:26:53 -04:00			`dokku ps:rebuildall # rebuilds all applications`
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			```
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
condense upgrading instructions + fix broken links 2016-04-20 15:32:52 -05:00			`To upgrade herokuish from source, upgrade with:`
Consolidate readme/wiki docs into organized docs folder 2014-10-04 04:24:22 -04:00
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			```shell
			`cd /tmp`
initial pass at switching to herokuish. closes #1091 2015-04-20 16:32:18 -07:00			`git clone https://github.com/gliderlabs/herokuish.git`
			`cd herokuish`
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			`git pull origin master`
[ci skip] remove unnecessary comments and update docs 2015-07-09 13:22:12 -07:00			`IMAGE_NAME=gliderlabs/herokuish BUILD_TAG=latest VERSION=master make -e build-in-docker`
[ci skip] update upgrade documentation for 0.3.18 2015-04-18 02:48:44 -04:00			```