That will just pull the latest image though right? I.e., if you explicitly have a container on a tag for v1.2.3, it wouldn’t upgrade you when v1.2.4 is released right?
That will just pull the latest image though right? I.e., if you explicitly have a container on a tag for v1.2.3, it wouldn’t upgrade you when v1.2.4 is released right?
To play devil’s advocate, tab completion would have also likely caught this. OP could have typed /mnt/t<Tab> and it would autofill temp, or <Tab><Tab> would show the matching options if it’s ambiguous.
I haven’t used it personally, I think Tailscale would help here. It sounds like it doesn’t require port forwarding, and uses Wireguard under the covers.
I’ve never heard of YumoHost, but I don’t get why preventing upgrades to an application deemed to have “issues” makes sense. If it has issues, wouldn’t you want to upgrade it when the issues are fixed?
One issue I can see with the points system is that people could just approve it with a “Looks good to me!” without even looking at the code. Or just looking at a small portion of the code.
Any idea what that first program was?
No, I mean doesn’t it only look for updates of the current tag? That works fine if you set every container to the “latest” tag, but if you set your containers to specific version tags then you won’t get a notification unless that specific tag gets updated.