Document and use coherent container tagging strategy

[ItsHarper]

What is the problem you are trying to solve with this feature?

I want to specify a specific version of homebox to run, not just whatever the latest one is.

I also would like the list of container tags to be more parsable.

It's most important for actual releases, but it might also be helpful to have clearer naming for the other containers as well. It's quite messy as-is: https://github.com/sysadminsmedia/homebox/pkgs/container/homebox/versions?filters%5Bversion_type%5D=tagged

What is the solution you are proposing?

Improve and document the container tagging strategy.

It seems like the latest release of homebox gets frequently rebuilt with the latest software from Alpine. A better naming scheme for these would be something like 0.22.3-YYYY-MM-DD-HH:MM:SS.

You could do something similar for the containers that get tagged as nightly and main .

What alternatives have you considered?

No response

Additional context

No response

Contributions

• I have searched through existing ideas in the discussions to check if this is a duplicate

[tankerkiller125]

Our tagging strategy is very straight forward.

• latest is the latest "stable" version build (still beta software).
• main is the main branch (only GHCR.io)
• nightly is built on a schedule at midnight UTC
• 0 is just the latest build
• 0.x is a specific "major" version with any patch version

Throw on -hardened or -rootless to the end of any of those for those specific version (hardened being distroless, rootless being rootless)