Skip to content
This repository was archived by the owner on Aug 14, 2024. It is now read-only.

Commit 2a78fbc

Browse files
committed
update
1 parent 734b585 commit 2a78fbc

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

src/docs/self-hosted/releases.mdx

+12-14
Original file line numberDiff line numberDiff line change
@@ -18,26 +18,24 @@ Sentry cuts regular releases for self-hosting to keep it as close to [sentry.io]
1818

1919
We encourage everyone to regularly update their Sentry installations to get the best and the most recent Sentry experience.
2020

21+
Before starting the upgrade, we shut down all the services and then run some data migrations, so expect to have some downtime. There is an *experimental* `--minimize-downtime` option to reduce the downtime during upgrades. Use this at your own risk and see [the pull request it was implemented in](https://github.com/getsentry/self-hosted/issues/607) for more information.
22+
23+
We assume you've cloned the self-hosted repository, so checkout the version you want to upgrade to (23.11.0 as an example).
24+
25+
```bash
26+
git fetch
27+
git checkout 23.11.0
28+
```
29+
2130
<Alert title="Warning" level="warning">
22-
If you upgrade infrequently, it's less likely that upgrading to latest will work.
31+
If you upgrade infrequently, it's less likely that upgrading to the latest version will work.
2332
Please refer to <Link to="#hard-stops">Hard Stops</Link> for how to incrementally upgrade to more recent versions.
2433
</Alert>
2534

26-
<Alert title="Configuration Updates" level="info">
2735
We may have some updated configuration, especially for new features, so always check the example config files under the <Link to="https://github.com/getsentry/self-hosted/blob/master/sentry/">sentry directory</Link> and see if you need to update your existing configuration. We do our best to automate critical configuration updates, but you should always check your configs during upgrades.
28-
</Alert>
29-
30-
Before starting the upgrade, we shut down all the services and then run some data migrations, so expect to have some downtime. There is an *experimental* `--minimize-downtime` option to reduce the downtime during upgrades. Use this at your own risk and see [the pull request it was implemented in](https://github.com/getsentry/self-hosted/issues/607) for more information.
3136

32-
To upgrade, all you need to do is download or check out the version of self-hosted repository you want, replace your existing folder's contents with that, and then run `./install.sh`. If you downloaded self-hosted repository using Git clone, the upgrade commands should look like this:
37+
Finally, to upgrade, just run `./install.sh`.
3338

34-
```bash
35-
# Assuming your destination upgrade version is 24.3.0
36-
VERSION="24.3.0"
37-
git fetch
38-
git checkout ${VERSION}
39-
sudo ./install.sh
40-
```
4139

4240
### Hard Stops
4341

@@ -47,7 +45,7 @@ These are the hard stops that you need to go through in order to pick up signifi
4745
<your.sentry.version> -> 9.1.2 -> 21.5.0 -> 21.6.3 -> 23.6.2 -> 23.11.0 -> latest
4846
```
4947

50-
Versions to avoid:
48+
Versions to avoid upgrading to:
5149
- `23.7.0` (issues around database migrations and the Django 3 upgrade)
5250

5351

0 commit comments

Comments
 (0)