From 87088539368afc71f7c46219c7f835ae78d0fa7f Mon Sep 17 00:00:00 2001 From: mirkan-samsung-wsl Date: Mon, 29 Apr 2024 02:56:19 +0300 Subject: [PATCH 1/4] Update Redash upgrade instructions and compose file --- .../kb/open-source/admin-guide/how-to-upgrade.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md index 11345eabc..d3f3c7e62 100644 --- a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md +++ b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md @@ -14,7 +14,7 @@ These instructions are for users of our new Docker-based instance. If you run ou We recommended you upgrade your Redash instance to the latest release so you can benefit from new features and bug fixes. This document assumes you used our images to set up your instance of Redash. -For best results you should upgrade Redash by one semantic version at a time. To move from V4 to V7, for example, you should upgrade V4 to V5 to V6 to V7. +For best results you should upgrade Redash by one semantic version at a time. To move from V4 to V7, for example, you should upgrade V6 to V7 to V8 to V10. During each migration, check the [releases page](https://github.com/getredash/redash/releases) for any special notices or breaking changes in the next version. @@ -22,6 +22,8 @@ Below is a table of recent docker release images for your reference: | released_at | version | docker_image | | ----------- | ------- | -------------------------- | +| 2021-12-24 | 10.1.0 | redash/redash:10.1.0.b50633| +| 2021-10-02 | 10.0.0 | redash/redash:10.0.0.b50363| | 2019-10-27 | 8.0.0 | redash/redash:8.0.0.b32245 | | 2019-03-17 | 7.0.0 | redash/redash:7.0.0.b18042 | | 2018-12-17 | 6.0.0 | redash/redash:6.0.0.b8537 | @@ -38,15 +40,15 @@ If you are currently running an instance of Redash prior to V7, **do not upgrade 1. Make sure to backup your data. You need to backup Redash's PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) and your `.env` file (if it exists). The data in Redis is transient. 2. Change directory to `/opt/redash`. -3. Update `/opt/redash/docker-compose.yml` Redash image reference to the one you want to upgrade to. -4. Stop Redash services: `docker-compose stop server scheduler scheduled_worker adhoc_worker` (you might need to list additional services if you updated your configuration) -5. Apply migration (if necessary): `docker-compose run --rm server manage db upgrade` -6. Start services: `docker-compose up -d` +3. Update `/opt/redash/compose.yaml` Redash image reference to the one you want to upgrade to. +4. Stop Redash services: `docker compose stop server scheduler scheduled_worker adhoc_worker` (you might need to list additional services if you updated your configuration) +5. Apply migration (if necessary): `docker compose run --rm server manage db upgrade` +6. Start services: `docker compose up -d` _Done!_ {% callout %} -**Getting an error when running `docker` or `docker-compose` commands?** +**Getting an error when running `docker` or `docker compose` commands?** Make sure the `ubuntu` user is part of the `docker` group: From 7743ad96e4d2b8d7693dd59ec448f770c7b77e3d Mon Sep 17 00:00:00 2001 From: "Restyled.io" Date: Sun, 28 Apr 2024 23:58:28 +0000 Subject: [PATCH 2/4] Restyled by prettier-markdown --- .../open-source/admin-guide/how-to-upgrade.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md index d3f3c7e62..06de1925f 100644 --- a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md +++ b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md @@ -20,15 +20,15 @@ During each migration, check the [releases page](https://github.com/getredash/re Below is a table of recent docker release images for your reference: -| released_at | version | docker_image | -| ----------- | ------- | -------------------------- | -| 2021-12-24 | 10.1.0 | redash/redash:10.1.0.b50633| -| 2021-10-02 | 10.0.0 | redash/redash:10.0.0.b50363| -| 2019-10-27 | 8.0.0 | redash/redash:8.0.0.b32245 | -| 2019-03-17 | 7.0.0 | redash/redash:7.0.0.b18042 | -| 2018-12-17 | 6.0.0 | redash/redash:6.0.0.b8537 | -| 2018-10-18 | 5.0.2 | redash/redash:5.0.2.b5486 | -| 2018-09-27 | 5.0.1 | redash/redash:5.0.1.b4850 | +| released_at | version | docker_image | +| ----------- | ------- | --------------------------- | +| 2021-12-24 | 10.1.0 | redash/redash:10.1.0.b50633 | +| 2021-10-02 | 10.0.0 | redash/redash:10.0.0.b50363 | +| 2019-10-27 | 8.0.0 | redash/redash:8.0.0.b32245 | +| 2019-03-17 | 7.0.0 | redash/redash:7.0.0.b18042 | +| 2018-12-17 | 6.0.0 | redash/redash:6.0.0.b8537 | +| 2018-10-18 | 5.0.2 | redash/redash:5.0.2.b5486 | +| 2018-09-27 | 5.0.1 | redash/redash:5.0.1.b4850 | {% callout warning %} From 6fb630ed2ac47a4c9cfecf3a787ecde71c35326d Mon Sep 17 00:00:00 2001 From: mirkan-samsung-wsl Date: Mon, 29 Apr 2024 03:04:08 +0300 Subject: [PATCH 3/4] // --- src/pages/kb/open-source/admin-guide/how-to-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md index 06de1925f..82c512976 100644 --- a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md +++ b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md @@ -40,7 +40,7 @@ If you are currently running an instance of Redash prior to V7, **do not upgrade 1. Make sure to backup your data. You need to backup Redash's PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) and your `.env` file (if it exists). The data in Redis is transient. 2. Change directory to `/opt/redash`. -3. Update `/opt/redash/compose.yaml` Redash image reference to the one you want to upgrade to. +3. Update `/opt/redash/docker-compose.yml` Redash image reference to the one you want to upgrade to. 4. Stop Redash services: `docker compose stop server scheduler scheduled_worker adhoc_worker` (you might need to list additional services if you updated your configuration) 5. Apply migration (if necessary): `docker compose run --rm server manage db upgrade` 6. Start services: `docker compose up -d` From 9c1eef60ac8dcaf46a6af87614d6000d6ef8e4f4 Mon Sep 17 00:00:00 2001 From: mirkan-samsung-wsl Date: Mon, 29 Apr 2024 03:07:25 +0300 Subject: [PATCH 4/4] // --- src/pages/kb/open-source/admin-guide/how-to-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md index 82c512976..7f61020e1 100644 --- a/src/pages/kb/open-source/admin-guide/how-to-upgrade.md +++ b/src/pages/kb/open-source/admin-guide/how-to-upgrade.md @@ -14,7 +14,7 @@ These instructions are for users of our new Docker-based instance. If you run ou We recommended you upgrade your Redash instance to the latest release so you can benefit from new features and bug fixes. This document assumes you used our images to set up your instance of Redash. -For best results you should upgrade Redash by one semantic version at a time. To move from V4 to V7, for example, you should upgrade V6 to V7 to V8 to V10. +For best results you should upgrade Redash by one semantic version at a time. To move from V6 to V10, for example, you should upgrade V6 to V7 to V8 to V10. During each migration, check the [releases page](https://github.com/getredash/redash/releases) for any special notices or breaking changes in the next version.