this post was submitted on 09 Jan 2025
1097 points (98.4% liked)
Programmer Humor
19935 readers
3332 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The container should always be updated to march production. In a non-container environment every developer has to do this independently but with containers it only has to be done once and then the developers pull the update which is a git style diff.
Best practice is to have the people who update the production servers be responsible for updating the containers, assuming they aren't deploying the containers directly.
It's essentinally no different than updating multiple servers, except one of those servers is then committed to a local container respository.
This also means there are snapshots of each update which can be useful in its own way.