I can't speak to the other points you made because this has always stopped me from investing in it. What I need in my stack is a focused Google Docs alternative, but every time I've installed it (3-4 times at this point) I'm quickly overwhelmed by the quantity of stuff it includes and by how complicated actually setting up the Docs replacement was (at the time the recommendation was to install Collabora and link it up with Nextcloud, which I never could get working).
What I did see out of the box was a slow and bloated web portal, a bad calendar, a bad video conferencing app, a file backup solution, and a terrifying app store filled with add-ons that may or may not be maintained. Oh, and now it looks like they have an AI assistant?
I'm honestly relieved to see this here and know it's not just me. I ended up going with Seafile for file backups and have been very happy with it, though I'd still love to find a focused collaboration tool I can run.
For collaborative editing LibreOffice Writer has a collaboration feature. Otherwise I’ll send a copy via message service of some kind (email, txt, chat, whatever) or download a copy to my Documents folder if someone sends me a google docs link or whatever.
Try Etherpad (https://etherpad.org/)
> I ended up going with Seafile for file backups and have been very happy with it
I went through probably dozens of solutions and ended up with Syncthing for synchronization of data (it requires understanding how it works but once you do (usually an eureka kind of moment) this is a very powerful system.
For me using synchronization software (Seafile, Syncthing, ...) to do backups is dangerous. Borg is a very good solution (or Restik, or Kopia)
Yep. Just synchronisation on its own for backup is at best better than nothing, a first step. It fails to protect from at least three very common occurrences you need backups for: accidental deletion, incorrect update, or corruption - the broken data is quickly synced everywhere. Adding snapshots and regular integrity checks is essential.
Seafile has file version history, so it's more than pure syncing and has so far been sufficient for backups, but I also run it on site so it's not safe in that sense and the data matters enough to be worth redundancy.
He should better use OnlyOffice, Collabora or Cryptpad office suite. The Cryptpad server is the only one which is not a nightmare to install and setup.
On that topic, it’s amusing to see when the “are we a product or a platform?” confusion jumps from its native host (publicly listed tech corps) to FOSS projects – different species altogether.
The idea of owning your own server just like any other device like laptops, smartphones and tablets, is just wonderful. But that means Linux! And Linux is absolutely infamous for poor application distribution (well technically the Linux distros). So now people make their own half-assed “app stores”, which is infinitely worse.
We would need a platform spec so that application developers can publish, users can discover and deploy, and platform providers can implement against a shared spec. That would be such a major step away from the surveillance economy and towards data sovereignty.
That’s right. And for UI, web is the obvious choice. But it’s not an application platform alone. You need at the very least file systems and networking/routing over https and maybe lower level protocol support too, that apps can use/discover without having to have a phd in Linux configuration. But to be truly useful, you need a lot more stuff wrt identity & auth, server-to-server networking, service discovery, cross-app communication, etc. Something more like Dokku probably.
> Or stuff like Helm, when you're talking about larger, more complex deployments?
Well fortunately you don’t need to open the Pandora’s box of consensus problems for a personal node (again like any other device). Also too much Yaml to make it sane probably?
That's been tried with Linux Standard base, but it seems 'standardise on glibc 2.31 and Qt 3' is not a viable way to describe system dependencies.
Such a spec also doesn't exist for Windows or macOS systems.
If you target 'living' operating systems you need living applications that are updated to keep working. We're well past the point you can assume some 20 year old binary will work unless you're running it in an emulator.
In a way, I have the same feeling. I really wanted it to work, but the install ( in my case via unraid ) broke multiple times after I started doing anything outside the basic functionality.
Eventually, I gave up on it and moved to dedicated apps for each portion I wanted and I have not looked back.
edit: syncthing for file sync wps-office for general doc work photoprism for pic library
The sync client on desktop said it was fully synced. Only 200GB of 800GB was on the machine.
It’s some of the worst software I have ever used. It’s the pentagon house with the inverted roof built with the two-clawed hammer that eevee described.
Did you read the manual? It is recommended for such size to do the first sync using rsync (or similar) followed by the CLI command to build the files database.
Not once had I any serious issues updating when pulling new updated images.
Occasionally it whines about missing indices, but that is easily fixed using the occ command line tool. The clients real IP is forwarded by the proxy.
What I want to say is just that Nextcloud works fine.
I've run it for about a year until the upgrade tipped me over. I am sure that correct upgrades (n to n+1) are fine - I tried n to n+2 and instead of explaining to me that this is not possible, Nextcloud explained to me that this is not possible and fucked up big my install. I had to recover from a backup.
The proper way would be to abort the upgrade upon discovering that I am going for an unsupported way.
This is not serious software.
If you don't support upgrading, don't expose that in the UI. There's no excuse for having UI that will let the user do something unsupported and then screw up their data.
Besides that, it is unethical and I wouldn't want to work at a company that pulls such stunts. I think a lot of people wouldn't. It'd be hard to keep secret, too, I mean, 5 years later the employee that was asked to do it works somewhere else and BOOM.
So all together, I think it's extremely unlikely to happen.
I CAN imagine a disgruntled ex employee or angry employee at a competitor would pull something like this. We have seen employees at a competitor create social media sock puppet accounts to spread FUD about us - but management at the competitor put a stop to that once we notified them.
if(target_version > current_version + 1) // not allowed
It's more work to add it to the docs than it is to put a fail-fast check in the upgrade script, so why put it in the docs where 250k+ admins need to be aware of the limitation and avoid it?It might be creating 100k hours of waste on the sysadmin side to save 30m of work on the dev side. I just don't get it.
Not saying it never breaks anything, but since 2016 we for example check PHP versions and other infra to not update to a broken system. We rewrote the updater in 2016 for this purpose. It's possible this has had a bug at some point of course - but it is more likely that the original poster who had this issue had this in the ownCloud times before 2016.
As soon as I started to add apps from the store it starts to be a pain. An upgrade comes out and you’re stuck on that version until they all update, OR you update not realizing and lose the functionality for some time.
Since I self-host a bunch of apps, it made more sense to use different apps dedicated to those features, like Miniflux or Navidrome. Not for everybody though.
Same idea, just safer and fewer surprises.
SHOT_TIME="$(date +'%Y-%m-%d_%H-%M')"
for dir in /docker/*
do
cd $dir;
btrfs subvolume snapshot "${dir}" "/docker/.snapshots/$(basename $dir)-${SHOT_TIME}"
docker compose pull --quiet
docker compose up -d
done
I mount a btrfs subvolume at /docker, and create a .snapshots subvolume inside.Each subvolume is an app and its dependencies, you want everything snapshotted as one. This is probably the biggest pitfall, if you don't take that snapshot of all the pieces.
/docker
|--> .snapshots
|--> app_one-2024-08-28_12-34
|--> app_one
|--> compose.yaml
|--> volumes
|--> app_one-config
|--> app_one-db
|--> app_two
|--> compose.yaml
|--> volumes
|--> app_two-config
|--> app_two-dbIt is constantly screaming for upgrades but I don't know what they are doing with those upgrades because it doesn't seem to make the core any more reliable. It's just an opportunity for the upgrade to fail and lose data, which it frequently took advantage of.
The key thing that really annoyed me is that I couldn't hardly have used it more lightly than I did, and it took about every other opportunity to fall over and lose data. I can't even imagine the plight of someone trying to run this in an office environment.
Also, what do iOS people do to make their auto upload folders upload automatically without having to open the app?
So i decided to switch to dedicated services, instead of using nextcloud to handle everything.
For images i can recommend Immich which is a new open source project specializing in storing your images with local AI support. I can highly recommend it.
I launched the container for the new version, but got an error: "Exception: Updates between multiple major versions and downgrades are unsupported."
I then tried launching the container for version 18, which should be supported, which initially seemed to succeed! However, I was greeted by "Internal Server Error" in the web UI, since apparently instead of just quitting, the initial upgrade had ruined the DB schema.
After restoring version 17 from backup, migrating to 18 and onwards, then trying to register my local apps with it, I then got CSP errors in the console when signing in. After manually editing the configuration file (which you seemingly can't do through environment variables) that seemed to be resolved.
Then, I tried syncing my local files but realized that the size of all of them is suddenly 0 KB. The files would show up in the web UI, but the size would be 0 KB. I had to rename the files a few times, which eventually fixed that, no matter how odd.
Finally, I realized that trying to open any of the pages in the web UI would take around 3-10 seconds. It seemed that there was a bug in the Talk application, disabling which then gave me the expected performance, even if it affecting how the Files application works also seems odd.
I like the utility Nextcloud provides me, but despise updating it. At this point I just stick to the core apps and wipe the whole thing when I need to update to something newer, manually carrying over the files I want to sync in the new instance.
Oh, also, out of the box the DB file locking configuration causes large file uploads (a few GB) to just hang, in a way where I cannot delete them. I had to disable locking altogether.
Honestly, it's just weird. If you need 1000 SQL migrations to go from version 1 of your software to version 20, just include all of them and don't mess around with disallowing migrating across multiple major versions. Same for any changes that might impact the persisted files on the FS. Just have updates be one continuous, long stream of patches, applied sequentially. If you do that and have sane defaults, you're good.
To not be overly negative: it's good that Nextcloud exists, is free, has a somewhat nice ecosystem around it and both the desktop apps and the phone apps for iOS/Android are okay.
My recommendation would be to use our All-in-One docker image. It takes care of updates and is supremely easy to use, plus likely to bring nice performance benefits as it has all this stuff that makes it fast like the HPB for Files.
I use the php script updater/updater.phar directly and that works just fine
Running it on k8s has similar issues. I only used it as sync for my obsidian notes with occasional (maybe once a month) access to those notes via web ui. I wasn’t happy with how it would reformat my notes on save.
Sync thing supports encrypted storage in VPS and is trivial to run in k8s and it’s been much better for my needs.
Look, it's not without its quirks, but it's pretty reliable. Speed and responsiveness can be further upped by using an in-memory cache like Redis/Valkey.
Nextcloud can try to be everything it wants, but as users we can ignore that and stick to file-sharing/online/cloud storage.
If one is using it primarily for file storage/sharing, it works reasonably well. We have ~1TB of Nextcloud data on an NFS share (itself snapshotted ZFS), backed up to B2 regularly.
If something happens to a Nextcloud server (and it has), restoring the data is as simple as recreating the users and copying over the data directory for each user (provided you're not using it for calendaring and such). A quick OCC command to re-index user data and we're back.
We haven't had any issues running the docker image (orchestrated via HCP Nomad).
We have also helped a friend run Nextcloud for their small non-profit, as a snap on an EC2 instance in AWS. It keeps itself up-to-date and has been pretty-much problem free for years. EBS Snapshots cover backups there.
Updates have never been an issue. And honestly I am always a bit surprised by that. I don’t update to a new version right away but when I’m ready, I change the version in the docker compose, pull, re-up the container. It performs the database migration and brings up everything. Never had an issue after using it for years. Not sure what your exact setup is, but it’s certainly not a nightmare to use.
They should make it the default, IMO.
Last week, I noticed that one of my contacts had an invalid date for their birthday. Try as I may, I cannot get Nextcloud to recognize 1/5/2000 as a valid date.
(And no, it's not a localization problem.)
There's like dozen scenarios where you end up with 0 byte files with no warning, error, etc. Sometimes it's an uploading issue, sometimes it's a syncing issue, etc. And they are still open, mutli-year, issues.
I ran into a version of it where existing uploads were replaced with zero byte versions, so I had to manually run a script to find them and I restore a pervious version. If it tried to do other things, like photos, document editing, collab, etc and did those poorly that would be fine. Failing at the most central task of just storing the data is not. It's still alpha quality, and if one intends to use it, it's critical you setup monitoring infrastructure to ensure file integrity (backups should go without saying).
I handle several nextcloud instances, one of them updated from owncloud, I'm very happy, it does a lot of stuff well and when you need specialized software you can because it's just files. Updates have been painless.
Wait until you see the "solution" for dealing with the client mangling timestamps [1]. After you've been burned by server updates, and then burned by client updates, with solutions that push the problems onto the system admin, you start to wonder if using it in the first place was a mistake.
IIRC, part of the reason they forked was because OwnCloud wasn't moving fast enough. My experience makes me think OwnCloud might have been right.
1. https://github.com/nextcloud/desktop/wiki/How-to-fix-the-err...
Yep. And any extra apps beyond the default just make upgrades go sideways. I've given up on it. Using syncthing instead (just for file syncing) and haven't looked back. It's not my favorite either, but just because it's a pain to configure. Once configured, it's been rock solid.
After giving up on Nextcloud I tried syncthing too - hated it - and most of that time was pandemic and not like I was syncing outside of my own home network.
Went back to dropbox instead (just for file syncing) and haven't looked back.
First if all, it wants to do everything and does none well (or better than specialized apps)
Its internals are a shitshow - a question about getting the real IP of the calling client raised a 10 pages discussion where people said "it works" and other days "it does not". The "solution" required you to change a volatile setting within the docker container (and do it again when the container changes)
Finally the upgrade is insane. I once tried to upgrade my installation, was told that n+2 upgrades are not possible (fair enough) and ... the installer destroyed the database. What a piece of crap. Thanks god for backups.