just about to do a pull down the latest
just about to do a pull down the latest version (1.0). Is there any adjustment that is recommended to the docker compose file? Or will the current one (am running v0.55.9) work without issue?
17 Replies
Hey if your docker-compose file is from 0.55.9 you're good to go with
Thank you
You're welcome ! Feel free to reach out if you face any issues !
Just done the migration (albeit a day late) and unfortunately it seems to have failed when rebuilding the stack.
Has the docker compose file changed?
I've got rid of the volume files as well, so a completely clean instance.
What migration have you done exactly ? ( from what version to what version )
What's failing also ?
Please feel free to find latest docker-compose here https://github.com/twentyhq/twenty/blob/main/packages/twenty-docker/docker-compose.yml
If we update it ( very rare ) we usualy do an alert
GitHub
twenty/packages/twenty-docker/docker-compose.yml at main · twentyh...
Building a modern alternative to Salesforce, powered by the community. - twentyhq/twenty
Just from 0.559 to the latest. Removed the volumes, then just stopped the stack and forced a refresh.
I'm running the stack on Portainer. Let me double check and use the docker compose file (though from first glance think they are identical).
yes. Docker compose is identical.
I'll rebuild and watch the log files
Logs tell a little bit:
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.4.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.4.2
npm notice To update run: npm install -g npm@11.4.2
npm notice
Then we get the following in the alerts section:
Ok..... it now seems to be working. The stack shows as inactive, but three of the four containers are working.
The ENV variables for the container haven't changed from v0.559 to v1
(just checked)
Could this be a redis issue?
Solved. For whatever reason, when the stack was built (using the compose file) it didn't launch the worker correctly (it was created, but then didn't run). I manually started the container, and seems now to be ok.
If anyone else potentially is doing the same setup, get them to manually start the worker container, then it should work correctly.