NC deck could be cool but I found it really disappointing.
NC deck could be cool but I found it really disappointing.
Sorry you’re getting down voted so much. I personally don’t have this problem, but if you do it’s a valid experience. UX is not easy to get right for the masses.
I’ve been running it for about 6 years, literally never did me dirty.
Docker compose pull every couple weeks, bump the major version whenever it’s time, migrations always work.
Nextcloud news is alright
Docker and docker-compose. Then learn podman after you have some experience, if you want to…
Or jump into kubernetes (or minikube) instead of podman if you want to do highly useful things.
But first, get comfortable building images with a Dockerfile, and then running them in a meaningful way, and networking them, and locking them down.
False.
I’m a big fan of running home stuff on old laptops for this reason. Most UPSs give you a few minutes to shut down, laptops (depending on what you run) could give you plenty of extra run time and plenty of margin for a shutdown contingency.
I used to use Ampache, say 14 years ago, and I liked it a lot. Until I ran an unrelated batch job to reorganize my music files that went sideways, and started streaming from Google music. I’ve been meaning to try it out again, or something like it.
They’re beating the algorithm
I don’t remember much about how to use kubernetes but if you can specify a tag like nextcloud:28
instead of nextcloud:latest
you should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.
There are varying degrees of version specificity available: https://hub.docker.com/_/nextcloud/tags
Make sure you’re periodically evaluating your site with https://scan.nextcloud.com/ and following all of the recommended best practices.
I have only ever run nextcloud in docker. No idea what people are complaining about. I guess I’ll have to lurk more and find out.
Things should not care or mostly even know if they’re being run in docker.
Always works great for me.
I just run it (behind haproxy on a separate public host) in docker compose w/ a redis container and a hosted postgres instance.
Automatically upgrade minor versions daily by pulling new images. Manually upgrade major versions by updating the compose file.
Literally never had a problem in 4 years.
I think this is great. It might be 1/1000th of these other systems, but I think the fediverse is at a tipping point where I’m not seeing the same things every day. I don’t think critical mass needs to be a ranked competition.
Let’s not pretend that the degenerate comment section in YouTube is peak high society though.
Or really any place where strangers mostly zing each other. It’s just like the opposite extreme of linked in
I installed it on Ubuntu server on my raspberry pi 4 and it took a couple months to fall over and become useless.
I’ve been running their OS since then and it has been absolutely rock solid. It’s been 5 or 6 years now, all I do is add more devices occasionally and update it when it occurs to me.
If you have a life and you don’t absolutely love tuning your OS for special purposes in ways that are already solved problems, the hass os image is the way to go.