Selfhosted

I seriously suggest you give Nextcloud another go, this time under Docker. Very simple to do.

Save the following in a new folder as docker-compose.yml

version: '3'

volumes:
  db:

services:

  nextcloud-app:
    image: nextcloud
    container_name: nextcloud-app
    restart: always
    volumes:
      - ./data:/var/www/html
    environment:
      - MYSQL_PASSWORD=changeme
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=nextcloud-db
    ports:
      - "80:80"
    links:
      - nextcloud-db

  nextcloud-db:
    image: mariadb
    container_name: nextcloud-db
    restart: always
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    volumes:
      - db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=changeme
      - MYSQL_PASSWORD=changeme
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

run this command in the folder -

docker-compose up -d

open http://localhost

I suspect nextcloud having performance issues with slow Disk IO. With rootless containers I had a much worse performance than rootfull. Also using MySQL Backend instead of SQLite did speedup the performance.

Nevertheless I have the same problems with nextcloud as you stated. Pretty much not as usable as I thought.

Just want to say that I've been there. There was a time my Nextcloud install was incredibly slow. Fortunately (or unfortunately?), it is featureful enough and widely supported that once you figure this issue out, it is a nice service to keep running.

For me, adding Redis was essential. It doesn't really make sense to me why (nothing I do on Nextcloud is intensive or data heavy) but it has greatly improved the performance of my app.

My entire setup is a containerized Nextcloud, Nextcloud Cron, MariaDB (if I knew Postgres was an option, I would've chosen that), and Redis:

version: '2'
services:
  nextcloud:
    container_name: nextcloud
    image: nextcloud:27-apache
    restart: unless-stopped
    environment:
      - MYSQL_PASSWORD=nextcloud
      - MYSQL_HOST=db
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
    labels:
      - 'public-service=true'
      - 'traefik.enable=true'
      - 'traefik.http.routers.cloud.rule=Host(`nextcloud.some.domain`)'
      - 'traefik.http.routers.cloud.tls=true'
      - 'traefik.http.services.cloud.loadbalancer.server.port=80'
    volumes:
      - /some/data/dir/nextcloud/data:/var/www/html
      - /some/external/dir:/wew:ro

  nextcloud-cron:
    image: nextcloud:27-apache
    restart: unless-stopped
    command: [/cron.sh]
    environment:
      - MYSQL_HOST=db
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=nextcloud
    volumes:
      - /some/data/dir/nextcloud/data:/var/www/html
      - /some/external/dir/:/wew:ro

  db:
    image: mariadb:10.4
    restart: unless-stopped
    environment:
      MYSQL_DATABASE: nextcloud
      MYSQL_USER: nextcloud
      MYSQL_ROOT_PASSWORD: nextcloud
    volumes:
      - /some/data/dir/nextcloud/db:/var/lib/mysql

  mysqldump:
    image: mariadb:10.4
    depends_on: [db]
    # restart: never # cronjob
    labels:
      - 'cron.schedule=0 0 8 * * ?'
    entrypoint: [mysqldump, -h, db, -u, nextcloud, -pnextcloud, --all-databases, -r, /out/nextcloud.sql]
    user: root
    volumes:
      - /some/data/dir/nextcloud/db-dump:/out

  redis:
    image: redis
    restart: unless-stopped

Nextcloud is not easy to setup, that´s right, but it is not this complicated. Use Postgres as database, it is faster than MySQL. Install Redis as Cache and configure PHP Cache too. This will speedup the most. I use nextcloud installed directly on the host, no docker. Another small guide is here for Postgres and Apache

For speed Seafile absolutely smokes Nextcloud.

If you create an account they'll give a pro license (limited to 3 users) for free. Or you can stick with the always free community edition which works great too.

I have nextcloud running on docker on a Raspberry Pi 4 and I'd say the performance is comparable to Onedrive web interface. If you're getting timeouts then something must be wrong with the setup, not the machine it's running on. Using Postgres instead of MySQL or using an SSD instead of HDD is not going to help your issue.

I have had issues with nextcloud breaking randomly every time ive tried it. The thing I wanted the most was the caldav/webdav to integrate with Gnome and Davx5 (and finally kill google calender), and to get that I tried Owncloud instead. The UI leaves a lot to be desired but if you only use the *dav functionality it works like a charm. It also has a mobile app for syncing and several extensions but I havent delved into them.

Nextcloud is hard to install in manual way (even sometimes with Docker). As far I know, both Snap and Yunohost versions of Nextcloud are solid. I used Snap version on the cheapest Linode VPS, and it worked fine, especially when I doubled the SWAP to 1 GB. Now I use Yunohost version and I have only good time with it. It is super stable, fast and reliable. I used Nextcloud_ynh on HP 800 Mini G3 with i5-6500t and now on Asrock Mini PC with Ryzen 7 5700g. It is working just great.

If you don't want to use Nextcloud, you ca install Vikunja for kanban and tasks. For notes Hedgedoc can be great.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

7 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

[Thread #125 for this sub, first seen 10th Sep 2023, 09:45] [FAQ] [Full list] [Contact] [Source code]

Nginx is supported and a good choice. What database are you using? I’d recommend MariaDB.

I run Nextcloud, its responsive and has all my stuff in it. Notes, Calendar, Contacts, Kanboard, Photos, RSS reader, others. You do need look at the setup, how many PHP processes are you running, how much memory does MySQL use.

My current setup is a a PHP vm, 6 cores and 8GB of memory and a MySQL vm that is 2 cores and 8GB memory. But I work for a SaaS provider and thats now we carve up our systems, a vm/instance for 1 job.

I'm my experience, nextcloud is quite I/O bound. The performance of your storage device will greatly affect nextcloud performance. But if you're already using SSD and the performance still bad, maybe there are other issues with your setup.

I guess you are doing something very wrong if you have such performance trouble all the time.

The Pi (up to 4) is known for bad disk I/O. Look into this area first.

I am running my nc on a weak old low power deskop CPU (and with real SATA harddisks) and only when I ask for long running jobs (like, create the previews and icons for 200 new photos) I can watch any slow responses at all.

Pydio and Seafile are alternatives I've tried. Pydio was pretty fast too. I agree with you on Nextcloud, I want to like it but I inevitably start having issues and it's slow even after tuning. It just tries to do too much and shouldn't be that complex to spin up a file server.

Go for the AllinOne (AIO) Installation! Had huge performance issues first (Nextcloudpi Docker & normal Nextcloud Docker) and none with the current install.

You get a self servicing (updates/installation/etc.) docker install with backups and administration portal.

It runs quite nicely on my Pi 3 with Apache and no Docker. I only use cloud storage, but the rest seems to work fine if needed. Maybe switching to a supported configuration would help?

• Problem with updating Nextcloud on TrueNAS - Lemmy.world
• Nextcloud on VM or Docker? Best set-up for proper backups? - Lemmy.world

For Kanban I use wekan, because it has more features. Nextcloud I host using snap, which I cannot 100% recommend because it sometimes has troubles upgrading to the latest version. Still, for me it causes less trouble than a manual install.