efrecon/bininstall

Binary Installers for Dockerfile Automation and GitHub Actions

Dear Reader 📖

I am slowly migrating all my docker-related work to an organisation, whalimeter

• 🗞 I seldom update my blog
• 🛠 I often create or update private OSS projects here, at bitbucket and gitlab
• 💰 I sometimes create or update corporate OSS projects, formerly at Yanzi, HealthIntegrator and Mitigram, now at GpsGate
• 💖 I have a special love for the misunderstood Tcl
• 🐚 Lately I have focused on POSIX shell to better target the embedded and devops spaces
• 🐳 I have a gist that, from a running container, prints out the command-line docker command to create it.
• 🐋 I have a script to rebase a slim Docker image on top of another one without changing its original configuration.
• 🏢 I am always open for opportunities in the beautiful Stockholm, or remote. But I am enjoying my time at GpsGate.

bininstall's Issues

Binary caching feature

When used as a GH action, both binaries would benefit from a binary caching feature, e.g. a -k/--keep command-line option that would express the number of seconds older, already downloaded binaries at the same location, should be kept in cache for. This would allow to keep binaries as part of the GH workspace directory on hosts for a few days, which is well compatible with the purpose of these scripts and action: download released, stable binaries for performing operations as part of a workflow job or a Docker image initialisation/operation.

Action examples

Provide simplified action examples directly as part of the main README.md and demonstrating the different inputs:

• Just a single URL input, e.g. a kubectl installation action taking the version to install from an environment variable.
• A URL with binary renaming, e.g. a jq installation action taking the version to install from an environment variable.
• One or two similar actions, perhaps something more relevant than act, that would install from a tar file instead. Maybe installing helm?