You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing on RepoCloud, I have version 0.11.2 that's pulled directly from GitHub (notice that it's even fresher than the latest release on GitHub, which shows 0.11.0).
But when installing to Render, it's pulling the image from Docker Hub (image URL: docker.io/twentycrm/twenty-front:latest). So I'm running an outdated image, 0.3.3.
The text was updated successfully, but these errors were encountered:
@charlesBochet So there's just one container then now that holds both BE & FE? Or are we supposed to run separate services still, just a single image is baked?
Scope & Context
At Docker Hub, the latest tag is 0.3.3: https://hub.docker.com/r/twentycrm/twenty-front/tags
While at GitHub it's 0.11.0: https://github.com/twentyhq/twenty/releases
The Docker Hub image should be updated for each new release.
Why it's important?
From the docs, it's suggested to install Twenty to Render or RepoCloud:
https://docs.twenty.com/start/self-hosting/cloud-providers
=> https://render.com/deploy?repo=https://github.com/twentyhq/twenty
=> https://repocloud.io/details/?app_id=259
When installing on RepoCloud, I have version 0.11.2 that's pulled directly from GitHub (notice that it's even fresher than the latest release on GitHub, which shows 0.11.0).
But when installing to Render, it's pulling the image from Docker Hub (image URL:
docker.io/twentycrm/twenty-front:latest
). So I'm running an outdated image, 0.3.3.The text was updated successfully, but these errors were encountered: