I tried Nextcloud a while back and was not impressed - I had issues withe the speed of the Windows sync that were determined to be “normal” with no roadmap to getting fixed. I’m now planning to move off Windows desktop so that won’t be an issue - so I thought I’d try again.

I went to nextcloud.com, clicked on Download-> Nextcloud server -> All-in-one -> Docker image - Setup AIO. This took me to the github README at Docker section. I’m already running docker for other things so I read the instructions, setup a new filesystem for my data directory and ran the suggested docker command with an appropriate “–env NEXTCLOUD_DATADIR=”. I’m then left with a terminal running docker in the foreground - not a great way to run a background server but ok, I’ve been around for a while and can figure out how to make it autostart in the background ongoing. So I move on to the next step - open my browser at the appropriate URL and I’m presented with a simple page asking me to “Log in using your Nextcloud AIO passphrase:”. I don’t have a Nextcloud AIO passphrase and nothing I’ve read so far has mentioned it. When I search for it I get some results on how to reset it, but not much help. I could probably figure that out too, but after reading some more I found that Nextcloud requires a public hostname and can’t work with a local name or IP address. I’m already running my home LAN with OpenVPN and access it from anywhere as “local” - I don’t really want to create a new path into my home network just for Nextcloud.

I’m sorry - I know this sounds like a disgruntled rant and I guess it is. I just want to check that I’m not missing obvious things before I give up again. All I want is a simple file sync setup like onedrive but without the microsoft.

  • rtxn@lemmy.worldEnglish
    12·
    22 hours ago

    I’ve never used the AIO image. I’ve heard it’s weird. This is my compose file for the community image:

    compose.yaml 
    volumes:
  db:

services:
  db:
    image: mariadb:10.6
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - db:/var/lib/mysql
    secrets:
      - mysql_root_password
      - mysql_nextcloud_password
    environment:
      - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password
      - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  nextcloud:
    image: nextcloud
    restart: always
    ports:
      - 8080:80
    depends_on:
      - db
    links:
      - db
    volumes:
      - /var/www/html:/var/www/html
      - /srv/data:/srv/data
    secrets:
      - mysql_nextcloud_password
    environment:
      - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db

secrets:
  mysql_root_password:
    file: ./secrets/mysql_root_password.txt
  mysql_nextcloud_password:
    file: ./secrets/mysql_nextcloud_password.txt

    You can access it on port 8080 and perform the initial setup manually. For the database server address, use the db hostname. You’ll have to use a reverse proxy for HTTPS.

    You could also try OpenCloud, which is a Go rewrite of ownCloud.

    • JASN_DE@feddit.orgEnglish
      7·
      22 hours ago

      You could also try OpenCloud, which is a Go rewrite of ownCloud.

      A fork of the internal Owncloud Go rewrite.

    • Great Blue Heron@lemmy.caOPEnglish
      2·
      20 hours ago

      I’ve never used the AIO image. I’ve heard it’s weird.

      It does seem to be. So, I find it weird that the “core” documentation leads a new user to installing AIO.

      You could also try OpenCloud, which is a Go rewrite of ownCloud.

      Sounds interesting - thanks.