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

Change default behavior of ENABLE DB MIGRATION (#9077)

Browse Source 
See:
https://github.com/twentyhq/twenty/issues/9031#issuecomment-2542015975

I think it would be easier if the default behavior for the container was
to run the migration, and setting the environment variable would be used
to disable it (e.g. on the worker).

Long-term goal is for the default setup to work out of the box with ~2
env variables only (database url, redis url)

I don't think there's a big risk if people forget to turn it off on the
worker?
This commit is contained in:
Félix Malfait
2024-12-16 17:31:45 +01:00
committed by GitHub
parent 449be46936
commit c90d2fd5cc
8 changed files with 17 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -20,6 +20,12 @@ If you used Docker Compose, follow these steps:
## Version-specific upgrade steps
### v0.34.0 to v0.40.0
- We replaced `ENABLE_DB_MIGRATIONS` with `DISABLE_DB_MIGRATIONS` (default value is now `false`, you probably don't have to set anything)
### v0.33.0 to v0.34.0
Upgrade your Twenty instance to use v0.34.0 image
@ -172,4 +178,4 @@ The `yarn command:prod upgrade-0.22` command will apply specific data transforma
<ArticleEditContent></ArticleEditContent>
<ArticleEditContent></ArticleEditContent>