Skip Navigation
frederic Frederic @chaos.social

Rage against the machine learning.

šŸ‘Øā€šŸ’» Spends too much time in front of computers. šŸ¤” Often starts things and doesn't šŸ„— Vegetarian. šŸŒ± Plant dad.

Interested in ā€“ not necessarily writing about: \#web #devops #monitoring #prometheus #ansible #homelab #linux #archlinux #flatcar #ttrpg #pnpde #pbta #tftl #monsterhearts #music #postpunk #darkwave

āœ… I'm not a robot. #nobot šŸ¤–

Posts 0
Comments 2
Updates vs. version pinning in Docker-based homelab
  • @RadDevon You can also use tools like Renovate or Dependabot to create a pull request once an image in your docker-compose files is updated (runs on GitHub, GitLab, Gitea, Forgejo, etc.)

    That leaves you with running tests in your CI pipeline and setting up a deployment step afterwards.

  • Updates vs. version pinning in Docker-based homelab
  • @RadDevon While using latest in a production environment is not considered a good idea, I've been using Watchtower in my homelab for years to keep running images up to date without any issue.

    Some apps also provide major version tags (e.g. Postgres), so you avoid breaking changes (as long as they adhere to semver).