dip — Docker Image Pusher

A small CLI that builds the Docker image in the current directory and pushes it to your registry under rolling semver tags (X.Y.Z, X.Y, X, latest).

Install

./install.sh

This requires uv. It symlinks pusher.py to ~/.local/bin/dip and creates ~/.config/docker_image_pusher/config.yaml. Edit that file to set your registry:

registry: registry.example.com/myorg

Make sure ~/.local/bin is on your PATH and that you are docker login-ed.

Usage

From any project folder containing a Dockerfile:

dip

• If VERSION.txt exists (image name then MAJOR.MINOR.PATCH, each on its own line; # comment lines are ignored), you are prompted to choose the next version: a bump level (major / minor / revision) or, if a version is found in a project file (package.json, pyproject.toml, etc.), that version as an extra option. Detected options that aren't newer than the current version are tagged (same as current) / (older than current) but can still be chosen.
• If VERSION.txt is missing, dip looks for a version in common project files (package.json, pyproject.toml, Cargo.toml, composer.json, *.csproj, pom.xml) and offers any it finds — letting you pick when there is more than one. The project name from those files prefills the image-name prompt. You can always enter a version by hand instead (default 0.1.0). That version is built and pushed as-is and the file is created. Odd version strings are coerced to MAJOR.MINOR.PATCH (e.g. 1.2 → 1.2.0, 1.2.3-beta → 1.2.3).

dip writes (and rewrites) VERSION.txt with a short comment header identifying the tool, e.g.:

# Created and managed by DIP (Docker Image Pusher).
# https://github.com/GrumpyMetalGuy/docker_image_pusher
my-image
1.7.3

dip then shows the tags it will push, asks for confirmation, builds, pushes X.Y.Z / X.Y / X / latest, and (on success) writes the new version back to VERSION.txt.

Development

uv run --with pyyaml --with pytest pytest        # pusher unit/integration tests
uv run --with pytest pytest test_install.py      # installer tests