Discussion: Automation of Updates #11

Open
opened 2024-08-19 15:54:06 -07:00 by Jafner · 1 comment
Owner

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.

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.
Jafner changed title from Discussion: Update Automation to Discussion: Automation of Updates 2024-08-19 17:31:42 -07:00
Author
Owner

In addition to Docker images, we should also look into methods of automating TrueNAS, VyOS, and Debian updates.

In addition to Docker images, we should also look into methods of automating TrueNAS, VyOS, and Debian updates.
Jafner added this to the Ongoing Cleanup and Paying Off Tech Debt milestone 2024-10-25 21:28:59 -07:00
Sign in to join this conversation.
No Label
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Jafner/Jafner.net#11
No description provided.