3 ms·
I had many of the same needs, so I wrote Harbormaster: https://gitlab.com/stavros/harbormaster https://gitlab.com/stavros/harbormaster All it does is manage C
by stavros 5y ago
I had many of the same needs, so I wrote Harbormaster:
https://gitlab.com/stavros/harbormaster https://gitlab.com/stavros/harbormaster
All it does is manage Compose applications, with a sane directory structure. It's been working great, both for my personal use and for a few companies running production workloads on it.
I love that it's super simple and the workflow it has is fantastic, I just push to a repo and everything else happens automatically.
- CGamesPlay 5y agoNice! I may even have looked at that when I was getting started on this project. The two things that jump out at me as "not as easy" are private docker repos and cron jobs. I know that you can run cron images for Docker, but I didn't want the extra layer of indirection.
- stavros 5y agoHmm, what do you mean? You don't have to use either of those with Harbormaster.
- CGamesPlay 5y agoI wanted to use both of them :)
- stavros 5y agoOh, well, you can :P Can you go into a bit more detail about your setup?
- CGamesPlay 5y agoNomad has native support for periodic jobs that does not require running a cron docker image, and that was a big draw. As far as the private registry goes, I don't see why that would be particularly hard with a set of compose scripts, but I really liked the fact that Nomad has everything about them documented. Honestly, if I had stuck with Compose files then Harbormaster looks like it's a reasonable way to manage them. But I felt like everything I wanted to do was just a little bit more difficult when I was using them, especially after comparing to Nomad.
- stavros 5y agoI see, thanks! Maybe cron functionality is something I can add, actually... It seems useful.