Opinion on nextcloud

[generalproxuser]

I know this is the proxmox forum but I wanted to just get honest opinions from others who may have used nextcloud.

I managed to get nextcloud installed inside a debian 11 lxc with php8. I also managed to move the data storage location from within the lxc vmdisk to my zfs pool. I am only interested in setting it up as a local LAN sync. I have a vpn server setup that allows me to connect into my LAN from the public world.

The big issue I saw is that uploads via the website or the davclient (mounting inside a windows machine as a network drive) is obviously slow. This is testing from within my LAN, not using the vpn connection.

When I upload the same file to my nfs or smb share that is on the same zfs pool (lxc container serving as nfs, tftp, smb server) the upload speed is more acceptable.

I was generous on the lxc resources (up to 8 cpus, up to 16gb ram) and I even tried messing with php settings. I just can't seem to upload a file at the same speed as when I direct upload via nfs/smb.

All that to ask the opinion: If I am connecting to my LAN via VPN and I have a working nfs/smb server that provides respectable upload speeds to the server from within the LAN, do I really need a nextcloud server?

 

[Dunuin]

Nextcloud is great, but I don't see the point using it just for local file sync. Great if you want to share files with people over the internet or work on something as a team, great if you want to selfhost all your cloud needs (bookmark/contact/calendar/todo synchronization) so you don't need to throw your privacy at Microsoft/Google/Apple. But for just local synchronization using a syncronization client that supports SMB/NFS shares or something like rsync would be faster and less to administrate.

I really like rsync as it can handle millions of files but it looks like there is no open source rsync client with GUI for Windows that is actually maintained. I used Deltacopy a long time but because it didn't got updates for years I needed to remove it because it was too outdated to work with the latest rsync server of my TrueNAS. Most other synchronization clients I tried like Puresync just can't handle that much files (problems comparing millions of files to find out what has changed).

 

[hevisko]

Depends on your use case, you might want a S3 compatible with some fun bells and whistles: Go check out minio ( https://min.io ) and make use of "rclone mount" for mounting it "locally"

NextCloud is for "roaming"/distributed file and information sharing and synchronization like contacts, calendars and permision controls between files shared between the various departments, NOT a high performance local LAN sync, for that: rather stay with NFS/SMB for local LAN.

The words that will slow down things: Webserver+PHP(permisions checks)+filestore, thus you are adding loads of complexity and slowing down stuff in the mix, and well.. it was never meant for high performance (ie. LAN speeds) file sharing.

Yes I am using NExtCloud, in the cloud inside a PVE

 

[generalproxuser]

After both your posts I re-evaluated my uses and at the very minimum I need fast file sync. Nextcloud is not up to the task. I am working on getting a seafile server running which is proving a challenge but that's part of the fun for me. I also tried spinning up a MyDrive-Storage server and that also presented some issues that I am working through. I glanced at syncthing and for personal reasons I will not be using that product.

Thanks for both of your posts as it got me onto a better? path for file syncing.

 

[generalproxuser]

I managed to get seafile going on a debian 11 lxc with bind mounts to my zfs pool for the seafile data location. Syncing is working, and the web gui uploads are significantly faster than what I saw in nextcloud. Coupled with my existing vpn setup and I don't even need to expose the seafile server directly to the public for file syncing. The files I need syncing are not shared with anyone for collaboration but I always need to be able to pick up where I left off. This fits the bill perfectly.