you are viewing a single comment's thread
view the rest of the comments
[–] 13 points 1 year ago (4 children)
  • [–] 3 points 1 year ago (1 child)

    This looks a lot more complicated that Watchtower. Is this something different or add other functionality?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    I'm not familiar with Watchtower, I assume it will restart the container/stack if a new image is found. The biggest difference is that an edit to the git repo causing the container to be redeployed. This means the git repo becomes the source of truth and its possible to redeploy even when config changes get merged.

  • source
  • parent
  • [–] 2 points 1 year ago

    I've been running this setup for a few months now and haven't looked back. Works super well, and essentially acts as an approval process for letting a container update or not.

    The author also recently added a followup article to this one for using Forgejo instead, made migrating the setup super easy.

  • source
  • parent
  • [–] 1 point 1 year ago

    Why this complicated setup? Komodo handles auto update by itself. It also update the whole stack at once, so no shutdown of the BD while the app stays up. Just have 2 checkboxes to tick.

    The less stuff the better, it's essential in case you have a failure. I only have to redeploy komodo, then all my stacks will be ready to get back online. I even removed watchtower.

  • source
  • parent