From 26bd01cbda0277d09b0eecb6193d7197901814ac Mon Sep 17 00:00:00 2001 From: Wyatt Johnson Date: Tue, 30 Jan 2018 15:29:36 -0700 Subject: [PATCH] updated docs for 4.1 release --- docs/_data/nav.yaml | 2 ++ docs/_docs/06-01-migrating-4-1.md | 35 +++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+) create mode 100644 docs/_docs/06-01-migrating-4-1.md diff --git a/docs/_data/nav.yaml b/docs/_data/nav.yaml index c765b0fb7..58e418c14 100644 --- a/docs/_data/nav.yaml +++ b/docs/_data/nav.yaml @@ -45,3 +45,5 @@ items: children: - title: Migrating to v4.0.0 url: /migration/4/ + - title: Migrating to v4.1.0 + url: /migration/4.1/ diff --git a/docs/_docs/06-01-migrating-4-1.md b/docs/_docs/06-01-migrating-4-1.md new file mode 100644 index 000000000..15caa7a29 --- /dev/null +++ b/docs/_docs/06-01-migrating-4-1.md @@ -0,0 +1,35 @@ +--- +title: Migrating to v4.1.0 +permalink: /migration/4.1/ +--- + +## Database Migrations + +We have unified the database verifications that were introduced in 3.x.x into +the migration system. This unification unfortunately required a database +migration bump. + +### Source + +When running via source, you can run the following to start the migration +process: + +```bash +./bin/cli migration run +``` +This will prompt you to perform a database backup before starting the migration +process. Data loss is entirely possible otherwise. +{: .code-aside} + +### Docker Compose + +If you are running Talk with docker-compose, you can use the following command +to perform the migration: + +```bash +docker-compose run --rm talk cli migration run +``` +This will prompt you to perform a database backup before starting the migration +process. Data loss is entirely possible otherwise. +{: .code-aside} +