2 ms·

Is there a reason for OCI images? It is just a binary? I have all used versions in ~/.local/bin/ ~/.local/bin/hugo0.145.0 ~/.local/bin/hugo0.148.0 ~/.loc

Is there a reason for OCI images? It is just a binary? I have all used versions in ~/.local/bin/ ~/.local/bin/hugo0.145.0 ~/.local/bin/hugo0.148.0 ~/.local/bin/hugo0.149.0 ~/.local/bin/hugo0.150.0 [...] and a convenience symlink ~/.local/bin/hugo, pointing to my "production" version. I can easliy call whichever version I like with hugo<tab><tab>. What am I missing?

wiether 6mo ago
It depends on your workflow I guess, but the advantages of having a Hugo version tagged in an image: - sharing it easily between computers/users (docker pull registry/image:tag) - having the appropriate binary version embedded in your code through a docker-compose in your repo - having custom aliases dedicated to hugo included (build/serve/run...) - using the exact same image in your CI/CD - not "polluting" your local computer with some more stuff