A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
From my experience docker seems to be best for me. I’m also no expert in any of this.
What I do is run the container in docker and then I user rsync to backup my files to both a secondary hard drive and off site storage with a backup provider.
I haven’t looked into database backups yet. Just files.
docker exec nextcloud-mariadb-1 /usr/bin/mariadb-dump --defaults-extra-file=/backup/.mylogin.cnf -u root --single-transaction --quick --all-databases |gzip > /mnt/mysql/backup/nc${NUM}_dump.gz
You are welcome
What would be the difference between this and creating a volume to the data directory and backing up that one?
I mean, is it not recommended? Is there a potential to backup in the middle of a DB transaction which would make the backup useless?
Exactly, you can end up with inconsistent DB state. Only possible filesystem level solution is take a LVM/btrfs/zfs snapshot and copy the DB files from there, but at that point, the dump is much easier and more convenient.
Im running nextcloud in docker from lsio atm. Doing daily file backups, so not database, mostly because it seems its pain to test backups, but also dont rly need anything else (at least not for now).
There is also a community !nextcloud@lemmy.world
First time I hear about running nextcloud in VM. Following to learn more.
I have the snap installed, for what it's worth it's pretty painless AS LONG AS YOU DON'T WANT TO DO ANYTHING SILLY
I've found it nearly impossible to alter the base behaviour and have it not entirely break, so if nextcloud out of the box does exactly what you want, go ahead and install it via snap...
I predict that on docker you're going to have a bad time if you can't give it host network mode and try to just forward ports
That said, docker >>>> VM in my books
Follow the official documentation https://docs.nextcloud.com/server/latest/admin_manual/installation/
Plain old webserver + php-fpm + database engine (I use postgres), no docker. People not following the recommended setup seem to have all kinds of woes (https://lemmy.world/comment/1981161)
Don't they offer an official all in one docker image?
It's more of a pain to get running than you might think for an official image. I got it running but definitely had issues getting started.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| SSH | Secure Shell for remote terminal access |
| SSL | Secure Sockets Layer, for transparent encryption |
2 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.
[Thread #34 for this sub, first seen 13th Aug 2023, 08:55] [FAQ] [Full list] [Contact] [Source code]
@notsofunnycomment Best set-up would be no Nextcloud at all. If you only use it for files, take a look at OCIS, SyncThing or Seafile.
What would be the advantage of running Nextcloud as a docker, instead of within a VM?
What would be a sensible way to have an incremental/differential backup of the VM/Docker?
The storage usage of my Nextcloud instance exceeds 1TB. If I run it within a VM, I will have to connect it to a 2TB SSD. Does it make sense to add the external storage space to the VM? [...]
In case you haven't yet, I'd also recommend taking a look at this: https://github.com/nextcloud/vm
It's basically a collection of three shell scripts to install, manage, and update Nextcloud. Last time I tried it also worked on LXC/LXD, not only VMs. It would probably work on Docker as well and has some files related to that in the migrate/docker directory.
If you can use containers always use containers as a rule of thumb. VMs are less efficient in almost every way and they add some unnecessary complexity.
For docker you basically only have to backup the persistent data. So in case of the docker setup you just have to backup the mounts and probably your compose file you are using. This probably also answers your third question already. Container files can be left alone and don't need to be considered for backups as they should be stateless and can reside in their default location (/var/lib/docker/overlay2 or so by default).
Overall it is quite simple as you only really have to consider the mounts and the docker setup. The mounts you define and should be really obvious and the docker setup is just a few config files at most or just the compose file.
My friend and I run most things in kubernetes (k3s), and then we use longhorn to backup volumes, which then can be re-used if your cluster crashes. Here's a blog post describing the process (although not for nextcloud specifically, it could be applied to Nextcloud as well, as we do this for nextcloud as well)