A Docker CLI plugin to push README files to container registries like Docker Hub, Quay, and Harbor.
docker-pushrm is a Docker CLI plugin that adds a `docker pushrm` command, enabling developers to update the README documentation of their container repositories directly from the command line. It streamlines the process of keeping container registry descriptions in sync with local documentation, improving project visibility and usability.
Container developers and DevOps engineers who publish images to Docker Hub, Red Hat Quay, or Harbor v2 and want to automate repository documentation updates. It's particularly useful for teams managing multiple container registries and integrating documentation updates into CI/CD pipelines.
Developers choose docker-pushrm because it integrates seamlessly with the Docker CLI, uses existing Docker credentials for authentication, and supports multiple major registries. Its availability as a container image and GitHub Action makes it uniquely suited for automation without requiring complex setup.
"Docker Push Readme" - a Docker CLI plugin to update container repo docs
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages existing Docker credentials for authentication, allowing it to 'just work' for logged-in registries like Docker Hub and Harbor, minimizing setup steps as stated in the README.
Works with Docker Hub, Red Hat Quay (cloud and self-hosted), and Harbor v2, covering major container registry providers as evidenced in the supported registries list.
Allows using a default README.md or specifying custom files like README-containers.md, with options for custom paths via --file flag, enabling separate documentation for registries vs. git repos.
Available as a container image and GitHub Action, with examples for GitLab CI/CD, making it easy to integrate into automated workflows without additional tooling.
Only supports Docker Hub, Quay, and Harbor v2, missing popular options like AWS ECR and GitHub Container Registry, with users encouraged to open issues for others, indicating incomplete coverage.
Requires creating and managing API keys through the Quay webinterface, involving steps like creating organizations and apps, which adds significant setup overhead compared to simpler credential-based logins.
While it can run standalone, full convenience depends on Docker CLI and credentials store; using with tools like Podman requires manual Docker-style config setup, adding complexity for non-Docker environments.