Redeploy on every Docker Hub push, without CI scripts
Use case · Updated on 12 October 2026
The problem
CI builds and pushes the image, and then someone still has to get it onto the server: an SSH step in the pipeline with a private key stored in CI, a script that pulls and recreates containers, or a watcher that polls the registry. Each test environment needs its own variant, and the key in CI can do far more than restart one service.
How it works in Enver
Enver gives a Docker Hub registry one webhook URL. After every push, Enver restarts – pulls and recreates – every running service in your account that uses the pushed repository and tag, in whichever environment it runs.
- Follow a branch with a tag. An environment whose
apirunsacme/api:developredeploys whenever CI pushesdevelop; production on1.8.0stays where it is. - No credentials in CI. CI only pushes to Docker Hub; nothing in the pipeline can reach your servers. The agent pulls the image with the registry credentials Enver keeps encrypted.
- The URL is the only key, and you can replace it. It can trigger only those restarts. If it leaks, Regenerate URL makes the old one stop working at once.
- Know when it’s live. Enver can send a push notification when a followed service starts running a new image – also a new build under the same tag.
Set it up
- Under Registries, add your Docker Hub registry with a username and access token.
- Click Set up Docker Hub webhook and copy the URL.
- On Docker Hub, open the repository → Webhooks and paste the URL.
- Run the services that should follow a branch on that branch’s tag, e.g.
developin dev andmainin staging. - Push from CI as usual and watch the environment restart.
Details are in the guide. Enver is free for up to 2 environments and 10 services – try it with your next push.
Questions
Which registries support the webhook?
Docker Hub. With other registries such as GHCR, GitLab or Harbor, Enver deploys the images too, and you switch tags in the browser or restart a service to pull a new build of the same tag.
Are stopped services redeployed too?
No. Only running services that use the pushed repository and tag are restarted; a stopped service stays stopped.
Does it work on Kubernetes environments?
Yes. A restart rolls the service’s pods, one by one when it has several replicas.