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!
Maybe because of my background, but I’ve never had an issue standing up or maintaining a Nextcloud instance. Especially since the AIO release. Hell, I was shocked how easy it was to migrate.
I’m not saying it’s the best software, but it’s always just worked. I’ve been using it since I dropped own cloud for the nextcloud fork. What common issues are people having with the infrastructure?
Yeah I'm really curious where the difficulty lies. Nextcloud was one of the earliest, if not the first, services that I deployed on a server when learning about Linux/Docker from scratch. The evolution of my setup has mostly been through my better understanding of container management practices than through anything Nextcloud specific.
My only Nextcloud specific issue has to do with the implementation of a reverse proxy (NPM) breaking the ability for my Nextcloud and OnlyOffice containers ability to connect - and I've not been so fixed about it that I haven't really sat down trying to figure a fix.
Not directly an issue, however I found NextCloud and OwnCloud to much bloated and not very responsive. I tried all the possible alternatives and they all had some strange drawbacks (proprietary database, chunked into some weired file format...)
Sure I could just use my nextcloud instance without all the possible add-ons, but I just wanted a simple and a reliable cloud service that just syncs my files between my devices without all the bloat.
My final argument would be that it is written in PHP... Programming language of the past ! While I'm probably wrong on this one and I do have no idea of the programming language realm and probably evolved over time, I do prefer something written in a newer more "secure" language.
So that's why I settled with syncthing. It's not a cloud service but a syncing service. It's different but has the same purpose in the end with more configuration options on how/where and when to sync between my devices.
As a final note (cauz I remembered something) 3 years ago I had a really hard time to make NextCloud work properly, via docker, with my reverse proxie (Treafik) I had to allow it manually in a configuration file and still didn't work great, but was probably my skill issues at that time :).
Probably you missed it: https://owncloud.dev/ocis/guides/ocis-local-docker/
Btw also ocis store the files in its own format
Another thing: migrate the data with rclone at the moment is not working very well , it’s easier to install a desktop client and copy the data with it
FWIW the file system it uses 'decomposedfs' can be read by other applications like rclone if needed.
Also ocis is working on a 'normal' file system with a few tradeoffs:
Interesting but I haven't found how to mount decomposefs with rclone, do you have any examples? I succeeded with WebDAV but it doesn't seem very reliable
Never done it myself but I think this example goes over the mounting
I'm not sure how to configure s3 as primary storage backend here. Should I put the configs in the ocis.yaml?
Here's an example configuration: https://github.com/owncloud/ocis/blob/master/deployments/examples/ocis_full/.env
here is my deploy:
https://github.com/simone-viozzi/my-server/blob/main/ocis_wopi/docker-compose.yml
be aware that i'm a couple of versions behind because there are breaking changes with no upgrade path. so i need to restart from scratch... and that's annoying.
i use trefik as a reverse proxy, and a subdomain for each service.
Seafile store data in its own proprietary format. There's no way to just go into the disk and browse the data. You need a proper backup solution.
In my case, I sync all my Seafile data between my server, laptop and desktop, so in the worst case I only lose the file history. A better option, if you have space, is to backup the Seafile storage volumes as well.
Seafile provides ready made compose files, with a detailed guide - https://manual.seafile.com/11.0/docker/deploy_seafile_with_docker/
Also, note that if you make an account on their site, you can get a free pro license for up to three accounts.