4 ms·
That's my preferred workflow for most internal services and things at home, and I got annoyed that there was nothing to automate them with, so I wrote Harbormas
by StavrosK 5y ago
That's my preferred workflow for most internal services and things at home, and I got annoyed that there was nothing to automate them with, so I wrote Harbormaster:
https://gitlab.com/stavros/harbormaster https://gitlab.com/stavros/harbormaster
You give it a config file with a few repos and it pulls/restarts whenever one changes.
- pc86 5y agoThis looks super interesting, I'm looking forward to digging into it more.
- stavros 5y agoThanks! Do let me know if it works for you, I love it so far but I've only deployed it in a few places.
- foolswisdom 5y agoIt's not clear to me from the README whether harbormaster will keep up to date with docker images in docker repositories as well. How does this work? Meaning to say, when there is a change to the repository, where do the new docker images come from? Use case is when a repository requires compilation to build the docker image, and I don't want that happening on the production server.
- StavrosK 5y agoAh yes, sorry, I should clarify this in the README: Docker images should be tagged in the repo (so you know what you're deploying), and Harbormaster will deploy the new image when you update the tag in the git repo. It doesn't currently check upstream Docker registries for changes like Watchtower does, mainly because I think that's not a deterministic enough way to do deployments (but that can certainly change).