Selfhosted
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:
- 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!
view the rest of the comments
I am using nextcloud for years now with postgres, redis and configured PHP setttings, but I installed it on the host. Never had any problems, Performance is awesome... Almost everytime I read about problems is with the docker images. The new AIO image shall be bad too, but I can not say anything to this, since I don't use it.
I really like docker, but sometimes it is better to install on the host directly or use an LXC if you need isolation. MinIO is the same... Would not want it in a Container
Maybe seafile could be an option for you π€
Docker has it usecases but I don't need everything in there. Like I said MinIO for example is just a short oneliner to start.
The most important thing is backup βΊοΈ
Bare metal club! :D
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 :)
Just wanted to +1 your comment. Installing on bare metal host is higher risk, but higher reward as well in terms of stability and performance. In my case Iβm using mariaDB, redis, php, and apache and itβs been solid for years now.
I used it with mariadb before, converting to postgres gave a performanceboost. Don't ask me why but it ran faster
If you are intrested, than here is a guide π
Iβm interested, itβs on the list but pretty far down. pgsql is better hands down imho but I followed nextcloud recommendations at the time I set things up and just never switched. Thanks for the guide!!
Been running multiple Nextcloud instances for years on bog standard debian + apache + php-fpm install, as documented in the official docs which do not even mention docker. Upgrades were never a problem. Some apps may suffer some bugs from time to time, but Nextcloud itself works flawlessly. Wrote an ansible role to install, manage and update it. The only thing that deviates from the "recommended" setup is Postgres instead of MariaDB. People need to start following the actual documented/well-supported installation options and stop trying to stick containers everywhere...
The docs are very good and you have a lot of tutorials for nextcloud, bit mostly they scratch only on the surface. They show you how to install and if you are lucky you see how to setup HTTPS....
But then? Start nextcloud and go to system overview and everything is red and you get warnings about region, php opcache... π Most tutorials end there. It is a pity
I just don't see how docker can fuck something like this up honestly, the only thing that can be screwy is permissions when dealing with filesystem mounts - but once you've got that working it should be pretty static.
Maybe it is permissions or the image won't start correctly. Maybe it tries to read from the database which is jot up at the moment or something similar π€
I use Seafile... can give a partial recommendation
I tried to run it on Debian and on each update it was always complaining the php version too old. Maybe on a distro that doesn't come with ancient packages can be ok...
I guess this is only a problem on an older debian server. Then you could use the PHP PPA. Some people still run PHP 7.4 or even 5.6, but they are end of life π³