admin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

[DOCS] Upgrade guide 0.53 (#12015)

Browse Source
This commit is contained in:
Paul Rastoin
2025-05-13 18:35:09 +02:00
committed by GitHub
parent fc4d313907
commit 6ac82b9591
1 changed files with 20 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
packages/twenty-website/src/content/developers/self-hosting/upgrade-guide.mdx
View File

@ -11,13 +11,11 @@ image: /images/user-guide/notes/notes_header.png
To restore backup, run `cat databases_backup.sql | docker exec -i <db_container_name_or_id> psql -U <postgres_user>`.
If you want to migrate from postgres bitnami container to postgres spilo container, you have to dump the database from the bitnami container and restore it to the spilo container using commands above.
If you used Docker Compose, follow these steps:
1. In a terminal, on the host where Twenty is running, turn off Twenty: `docker compose down`
2. Upgrade the version by changing the `TAG` value in the .env file near your docker-compose.
2. Upgrade the version by changing the `TAG` value in the .env file near your docker-compose. ( We recommend consuming `major.minor` version such as `0.53` )
3. Bring Twenty back online with `docker compose up -d`
@ -27,12 +25,20 @@ If you want to upgrade your instance by few versions, e.g. from 0.33.0 to 0.35.0
## Version-specific upgrade steps
{/* ### Since v0.53
We've now added `yarn command:prod upgrade` to the [entrypoint.sh](https://github.com/twentyhq/twenty/blob/main/packages/twenty-docker/twenty/entrypoint.sh#L19) file.
This means from now on, you shouldn't have to run any command manually anymore.
Just make sure to keep upgrading your instance sequentially, without skipping any major version (e.g. 0.43.3 to 0.44.0 is allowed, but 0.43.1 to 0.45.0 is not).
You can view your instance version in the admin panel (at /settings/admin-panel, accessible if your user has canImpersonate property set to true in the database). */}
### Since 0.53
Starting from `0.53`, upgrade is programmatically done within the `DockerFile`, this means from now on, you shouldn't have to run any command manually anymore.
Make sure to keep upgrading your instance sequentially, without skipping any major version (e.g. `0.43.3` to `0.44.0` is allowed, but `0.43.1` to `0.45.0` isn't), else could lead to workspace version desynchronization that could result in runtime error and missing functionality.
To check if a workspace has been correctly migrated you can review its version in database in `core.workspace` table.
It should always be in the range of your current Twenty's instance `major.minor` version, you can view your instance version in the admin panel (at `/settings/admin-panel`, accessible if your user has `canImpersonate` property set to true in the database) or by running `echo $APP_VERSION` in your `twenty-server` container.
To fix a desynchronized workspace version, you will have to upgrade from the corresponding twenty's version following related upgrade guide sequentially and so on until it reaches desired version.
### v0.51 to v0.52
@ -43,6 +49,12 @@ yarn database:migrate:prod
yarn command:prod upgrade
```
#### I have a workspace blocked in version between `0.52.0` and `0.52.6`
Unfortunately `0.52.0` and `0.52.6` have been completly removed from dockerHub.
You will have to manually udpate your workspace version to `0.51.0` in database and upgrade using twenty version `0.52.11` following its just above upgrade guide.
### v0.50 to v0.51
Upgrade your Twenty instance to use v0.51 image