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?


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.


IMO, setting it up at home is not the bar for decentralization. I don’t think it’s even practical to run your own self-hosted fediverse server.
I think we can get just about all the same benefits of decentralization at the scale of the city.
Assuming a constant rate of change of anything involving people over a period of ten years is straight up nonsense.


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.


I think it’s a good idea, everyone should be automating this anyway.
This is still not possible in all scenarios. For example, wildcard certificates for DNS providers with no API support.


You both aren’t wrong… But this isn’t about you.


I spent an unhealthy amount of time on Reddit. Getting bored of Lemmy is a feature, not a bug. Embrace it.


I dunno. You could throw yourself down the stairs. It’s an awful choice, but you could still do it…
The point is, a choice with all kinds of negative consequences to it isn’t really a choice.


Terminals are powerful and flexible, but still slower than a dedicated UI to see states at a glance, issue routine commands, or do text editing.
Terminal absolutists are as insufferable as GUI purists. There is a place and time for both.


You should perhaps skim through https://docs.docker.com/storage/ quickly. That document explains that docker containers only have very limited persistence (this is kind of the whole point of containers). The only persistence of note is volumes. This is normally how settings are saved between recreating containers.
As for dependencies, well it’s possible that one container depends on the service of another. Perhaps this is what you are describing?
Either way, for more detailed help, you will have to explain your setup with more specific technical details.


Just a thought, communities dedicated to one particular gender are often not inclusive by design, especially if you actively try to funnel people of a certain gender to certain communities. And therefore they, historically, have tended to devolve into echo chambers, and then subsequently into toxic spaces, with little room for nuanced discussion nor hosting a broad range of opinions. That’s not to say all communities are like this and most don’t start out like that either. There is value to have these communities if they themselves promote inclusion. But putting people of a particular gender into a gender-specific community is not at all the solution to “Too few women on Lemmy”.
I’d rather see the focus on making the general communities be welcoming to everyone equally.


No one else uses the term “cloud” like that.
That part of this comic really stuck out like a sore thumb. I can’t tell if it’s an oversight, a comment about the challenges of self-hosting, or subtle mockery of self-hosting hypocrisy.


“Government” is a pretty broad term. It encompasses both elected or ruling leaders that implement policy (politics), as well as the administrative beaurocracy that implements whatever policy is enacted day to day. It’s pretty typical for the beaurocracy to continue functioning under whatever mandate they have and even to make their own descisions if the mandate gives them that latitude, even if the leadership part of the government is being changed or otherwise non-functional.


I guess people forgot how the internet itself used to be a “monoculture” of nerds and weirdos. Weirdos and nerds have been making the cool trendy places that the mainstream first shuns and mocks then flocks to (maybe “ironically” at first) for centuries. Maybe even millenia.


Information is power. Information is used against you pervasively for control. This control ranges in nefariousness. You want examples? Here are some examples of consequences of use of information as a means of power:
The usual response to a list like this goes something along the lines of, bah, none of that will happen to me, I’m a goody-two-shoes. That advice is about as good as saying “I’m a good driver, I won’t get into a crash, so I don’t need to wear a seatbelt”. Back to my point, the consequences of information used against you are too far and too abstract for people to accept.


The problem isn’t that people don’t care. The problem is that the negative consequences are too abstract/too far to see. Not so different than smoking or climate change denial.
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.