Change default behavior of ENABLE DB MIGRATION

[FelixMalfait]

See: #9031 (comment)

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?

[greptile-apps]

PR Summary

This PR modifies the Docker entrypoint script to enable database migrations by default, requiring explicit disablement rather than enablement, aimed at simplifying the initial setup process.

• Changed condition in /packages/twenty-docker/twenty/entrypoint.sh from requiring ENABLE_DB_MIGRATIONS=true to running unless ENABLE_DB_MIGRATIONS=false
• Impacts worker containers which may need explicit ENABLE_DB_MIGRATIONS=false to prevent duplicate migrations
• Relates to SERVER_URL redirection issue (Docker Compose Upgrade to 0.34 breaks Redirect #9031) as part of broader Docker configuration simplification
• Could affect existing deployments that rely on migrations being disabled by default
• Documentation in /packages/twenty-website/src/content/developers/self-hosting/upgrade-guide.mdx should be updated to reflect this change

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[Weiko]

false?

[Weiko]

LGTM