Are you updating 1000’s of stacks every week? I update a couple critical things maybe once a month, and the other stuff maybe twice a year.
I don’t recommend auto updates, because updates break things and dealing with that is a lot of work.
Are you updating 1000’s of stacks every week? I update a couple critical things maybe once a month, and the other stuff maybe twice a year.
I don’t recommend auto updates, because updates break things and dealing with that is a lot of work.
Documentation is for onboarding other people. Why on earth would I need to onboard other people to something self-hosted?


You would be correct for a switch only, but not a router (serving multiple VLANS and/or hosts via a trunk port connected to a single switch or WAP). https://en.wikipedia.org/wiki/Trunking


What are the odds it’s self sabotage in an attempt to force the ship to leave.


It all makes sense if we remember that the garden variety AI we have today (ChatGPT, etc) are nothing more than fancy models that predict which words typically appear one after the other in books and reddit posts.


I enjoyed the depth of this answer. That being said…
4 copies seems like a level of paranoia that is not practical for the average consumer.
3 is what I use, and I consider that an already more advanced use case.
2 is probably most practical for the average person.
Why do I say this? The cost of the backup solution needs to be less than the value of the data itself x the effort to recover the incrementally missing data x the value of your time x the chance of failure.
In my experience, very few people have data that is so valuable that they need such a very thorough backup solution. Honestly, a 2$ thumb drive can contain most of the data the average user would actually miss and can’t easily find again scouring online.


It’s a very easy movie, almost guaranteed to work, and makes them money. I don’t know why they’re not doing it.
Probably because export tariffs make your product less appealing to import compared to other potential competing exporters who don’t collude on an export tax, or the target country who might be incentives to produce domestically instead of importing. Obviously, some industries are more geographically locked than others, but these deals still have knock on effects.


Anecdotally, it has made things worse. The shopping bags were already being reused as garbage bags, now I have to buy rolls of single use plastic bags instead. Worse, those tote bags are everywhere now, and so much less ecological.


Sounds like the Narcissist’s Prayer to me.


OP didn’t specifically say “only use the parts that came out of the box”. It’s still ambiguous. Are official mods, like PRUSA MMU modifying? How about after market parts?
Let me propose a modification tier list:
I’ve personally done all 5. I can’t imagine everyone has done all tiers of modifications.


Well yes, this was the original intent of crypto. Putting payment in the hands of the people. It’s only been made terrible by tech bros and greed the same way the Internet has.


Believe it or not, authoritarian regimes are less stable than democracies.


A broken clock is right twice a day. Inventions are only good when they reliably work for all the intended solutions.


Surely the SVGO package can be compiled into a browser bundle.
I might look into this myself…


Does this support SVG, i.e. SVGOMG/SVGO? If not, that’s a glaring omission.
Horses can go places cars cannot. You have completely missed the point.


This is the best way to stick it to fascists.
Cool. Now do the USA next.
I guess it depends what you run, and how the projects/containers are configured to handle updates and “breaking changes” in particular.
But also, I’m being a bit broad with the term “breaking changes”. Other kinds of “breaking changes” that aren’t strictly crashing the software, but that still cause work include projects that demand a manual database migration before being operational, a config change, or just a UI change that will confuse a user.
The point is, a lot of projects demand user attention which completely eclipses the effort required to execute a docker update.