No that’s a homelab. Selfhosted applies to the software that you install and administrate yourself so you have full control over it. If it was about running hardware at home we’d see more posts about hardware.

lol “Selfhosted” my ass - that’s why FOSS is superior regardless of features.

Strange survey - it seems to imply that self-hosting means that I have the hardware running at home? Cannot fill this out, unfortunately.

It has an O-counter, something I’d not use in an app that hosts my family videos.

TBH I’m migrating manually by synching files. Still wonder if it’s worth the hassle to somehow export/import contacts & calendar instead of reproducing them by hand. I thought about feeding the mariadb the psql dump I used to create for backups but that’s probably more work than doing things by hand.

One reason for me to try docker is “easier” backup. I just throw the whole data-directory of the db container into restic. Restoring the backup would just be starting a container with that saved directory. I hope that way I don’t have to argue with the database about reading a huge sql dump.

Unfortunately the documentation is a bit weird, I think. There’s the official all-in-one container that starts a container that starts more containers but that was a bit too much “magic” for my taste. I used the images and documentation maintained by the community here and ended up with this compose file I can manage in portainer. Runs nextcloud (with apache), mariadb and redis. Also had to add that final bit for the cron job. This way I can point my reverse proxy at the local ip of the nextcloud_apache container and be done with it.

That’s how I ran my nextcloud for about a decade and never had problems. On my new server I’m running it in docker and so far it seems to work ok.

I wondered about that myself these days and decided to give each stack its own db. Makes it easier to throw a stack into the bin without having to manually prune the associated databases. I might end up running a database container anyways for tests and side projects and things like that but service stacks get their own db of their choice.

Looks like the rust-cult is at it again rewriting existing stuff for no gain but pushing rust on others.

While I don’t agree that using something like restic is overkill you are very right that backup process monitoring is very overlooked. And recovering with the backup system of your choice is too.

I let my jenkins run the backup jobs as I have it running anyways for development tasks. When a job fails it notifies me immediately via email and I can also manually check in the web ui how the backup went.

I think they had some form of cloud computing at some point but they now focus on B2 and some backup tools that utilize B2.

Yes it’s their cloud storage.

“bloat” is thrown around so lightly that it loses all meaning.

Except for when it stops working and you find your files on the server are scattered in their proprietary format.

Cannot confirm this. For me nextcloud is very snappy and fast.