this post was submitted on 02 Aug 2023
133 points (91.3% liked)
Selfhosted
60482 readers
961 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Good to hear that it is running ☺️
Did you follow a specific guide or did you migrate yourself? Which image are you using? Maybe this could help others
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.
Thanks for the input. Copy over files is the "clean" way, without struggle, yes. For backups I use rclone and copy the userdata folder encrypted to external storage. Works fine for me. Maybe your dokcer files will help others, thanks for sharing :)