Replies: 3 comments
-
|
I would just manually change the version tags then: Using latest tags is not recommended as it may have some breaking changes. |
Beta Was this translation helpful? Give feedback.
-
|
For now I have used the I am curious though, but assume that @ggogel verifies if a new release works before pushing the |
Beta Was this translation helpful? Give feedback.
-
Yes, most likely he does verify it. But sometimes mistakes happen, so I feel its better to be safe than to be sorry. 😉 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So, I found this containerized version of seafile. It is a much more transparent and well configured docker way of deploying seafile. Looking at the docker-compose file I noticed specific version tags for all images. This makes sense, since it is known stable config. But as time progresses it will likely be updated. I could go into my adapted docker-compose file and update accordingly as new versions are posted here. However, a more lean and mean way would be helpful, where I do not have to update the version tags manually when a new release of the docker images is being pushed onto docker hub.
So I looked at the different versions hardcoded in the docker-compose.yml file, and noticed the following:
ggogel/seafile-server hardcodedversion tag (11.0.7 as of writing) is same aslatestggogel/seahub hardcodedversion tag (11.0.7 as of writing) is same aslatestggogel/seahub-mediaversion tag (11.0.7 as of writing) is same aslatestmariadbversion tag (10.11.7 as of writing) is same asltsmemcachedversion tag (1.6.26 as of writing) is same aslatestggogel/seafile-caddyversion tag (2.7.6 as of writing) is same aslatestSo I assume replacing the version tags with the corresponding label tags, would keep things in line with the latest release. Then, when a new version is pushed by ggogel, just rerunning docker compose would pull the latest versions out. Obviously this may introduce a risk of getting errors, but done manually this should be easy to overcome I guess. Is this a valid update strategy, even in a somewhat production environment?
I am wondering what the best update strategy would be. And would like to discuss what would be recommended.
Beta Was this translation helpful? Give feedback.
All reactions