Open renatobellotti opened 4 years ago
Sure, though we would need to move it under the etesync/ namespace for that.
which container is ready for production?
@tasn Can we consider victor-rds's images as official ? @victor-rds Do you have CI/CD to automatically build and release an image when a new version is available ? Also
victorrds/etesync
andvictorrds/etebase
seem to be mirrors. Should I rather usevictorrds/etebase
?Thanks for you work all !
There is CI/CD to generate the images, but I must trigger manually each new version, the only automatic dependency check is the python's docker base image (currently broken on 3.10.0), I'm learning how to use renovate to automate the build based on github releases version, no ETA for that yet.
Yes, both tags (victorrds/etesync
and victorrds/etebase
) are the same build, I've changed the git repo name but keep the pushing victorrds/etesync
to avoid breaking automated installations, I use the victorrds/etebase
.
I would love to give self-hosted etesync a try, but I'd like to run it on docker. I'm willing to try this on my own, but I will probably need some time to get it right... I will share my results once I have a working solution!