sync_install

sync_install is a CLI which updates what is installed by comparing two Dockerfiles.

Installation

cargo install --git https://github.com/DenisNavarro/sync_install --tag 0.11.0 --locked

Usage

For example, if the content of the current_state file is:

FROM docker.io/library/rust:1.90.0-slim-bookworm
RUN set -eux; \
    cargo install cargo-cache --version 0.8.3 --locked; \
    cargo install cocogitto --version 6.3.0 --locked; \
    cargo install fsays --version 0.3.0 --locked; \
    cargo cache -r all
CMD ["/bin/bash"]

and if the content of the target_state file is:

FROM docker.io/library/rust:1.90.0-slim-bookworm
RUN set -eux; \
    cargo install cargo-cache --version 0.8.3; \
    cargo install cocogitto --version 6.3.0 --locked; \
    cargo install pixi --git https://github.com/prefix-dev/pixi.git --tag v0.55.0 --locked; \
    cargo cache -r all
CMD ["/bin/bash"]

then the output of sync_install current_state target_state will be:

This is a dry run. Add the --go option to execute the below command(s).
---> [cargo uninstall fsays]
---> [cargo install cargo-cache --version 0.8.3 --force]
---> [cargo install pixi --git https://github.com/prefix-dev/pixi.git --tag v0.55.0 --locked]

Warning: This program is limited to a few use cases of its author and the format of the Dockerfile contents must follow some arbitrary rules.

Tip: Update by comparing a Dockerfile to its state in the Git index:

sync_install <(git show :./Dockerfile) Dockerfile
sync_install <(git show :./Dockerfile) Dockerfile --go

If you wonder what features are implemented, you can look at the corresponding unit tests.

Then, if you wonder what are the arbitrary format rules, you can look at more unit tests.

Remark

The unpublished previous version of this CLI read two YAML files instead of two Dockerfiles, but it did not fit my use cases.

A Dockerfile is more flexible and can be used as a checkable documentation.