Nightly naming siggestion #10700
diyoyo
started this conversation in
Development
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I don't know whether this has already been discussed on Discord, but I find it confusing to have all nightlies be called "main". Like on docker hub, it is not possible to fetch the nightly of a specific date, or even to know on which release base it relies.
My humble suggestion would be to name it according to base version and publication night, like
or something like it. Then on Docker Hub, one could fetch it :
When keeping multiple instances up to date, it is easier to perform backups if we know which image it is based on.
Right now, if I want to go from one nightly to the other, and perform a backup first, I have to re-tag the current image first, save the whole data+image first, then only I feel safe upgrading to a newer version. But then I need to upgrade all the instances I have. If not, the only strategy available currently is to retag the image right after pulling it, before starting the container of a specific instance....
Same goes for Desktop: I made scripts that track which instance uses which nightly, because when creating a new instance, I always download the latest nightly, but I don't necessarily update the other instances.
(Btw, I'm using "instance" to refer to the data inside the db)
All reactions