Discussion: Automation of Updates #11
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Jafner/Jafner.net#11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We want to minimize toil, but thus far our strategy for this in our image updates is to defer until we need a fix or feature introduced in a more recent version.
Rudely, the people that work on the open source software that I use in my lab don't stop working on their projects after I pull an image. So as the planet keeps turning, our deployed images become more out of date.
I want to start a discussion here about possible tools and strategies for managing and automating upkeep of our Stacks, especially as relates to Docker images.
Discussion: Update Automationto Discussion: Automation of UpdatesIn addition to Docker images, we should also look into methods of automating TrueNAS, VyOS, and Debian updates.