Comment on Nextcloud appreciation post

stuckgum@lemmy.ml ⁨6⁩ ⁨months⁩ ago

• ksp@jlai.lu ⁨6⁩ ⁨months⁩ ago

  Using Nextcloud AIO takes that pain away if you are into Docker. It has everything needed bundled in it, including a db and web server.

  source

  • peregus@lemmy.world ⁨6⁩ ⁨months⁩ ago

    I was surprised to know that there is no tool to pass from Nextcloud to AIO.

    source

    • ksp@jlai.lu ⁨6⁩ ⁨months⁩ ago

      That’s saddening. I think that best you can do is a backup of your data and restore it when using AIO is setup

      source
• words_number@programming.dev ⁨6⁩ ⁨months⁩ ago

  docker-compose up -d

  Oof what a pain this was! Glad it finally works and I can move on with my life!!

  source

  • helenslunch@feddit.nl ⁨6⁩ ⁨months⁩ ago

    TIL “setting up and tweaking Nextcloud to your liking” = starting docker

    source
  • hperrin@lemmy.world ⁨6⁩ ⁨months⁩ ago

    Hey hey hey. That’s not fair. You also have to

    sudo apt install docker.io docker-compose

    source

    • princessnorah@lemmy.blahaj.zone ⁨6⁩ ⁨months⁩ ago

      You really should not install those from the distro repositories. They are far less up-to-date. This is the official documentation for adding the Docker repository to a Debian system, there’s one for Ubuntu as well. You can just copy and paste the entire code block from step 1. Afterwards you can just use apt to install it, but you want to use this command to make sure you get everything you need:

      sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

      Installing it this way will mean you need to use the docker compose command, not docker-compose which is deprecated.

      source
• x3i@kbin.social ⁨6⁩ ⁨months⁩ ago

  True. Have a setup running on Kubernetes with their helm chart but the documentation is (or at least was) insufficient on what is important to back up, so I had to start over once, learning the hard way that the config file contains the one string you always need for recovering data. Since then, it is pretty stable and I had almost no problems.

  source

  • moonpiedumplings@programming.dev ⁨6⁩ ⁨months⁩ ago

    What was it? I’m planning to do a nextcloud deployment via helm soon.

    source

    • x3i@kbin.social ⁨6⁩ ⁨months⁩ ago

      Update: seems like the persistence section is sufficient; I have

      persistence:
        enabled: true
        existingClaim: nextcloud-config-claim
      

      at the end of my values file which references a volume claim (and volume) that I created manually upfront. The importand file is config.php. Back that thing up immediately and three times, print it if you have to. The secret in there is unrecoverable otherwise and needed for any repair actions.
      I also use the postgresql sub-chart (by simply enabling postgresql as database) and provide a claim there:

      postgresql:
        enabled: true
      global:
          postgresql:
            auth:
              username: XX
              password: YY
              database: nextcloud
        image:
          repository: postgres
          tag: "14"
          postgresqlDataDir: /bitnami/pgdata
        primary:
          persistence:
            enabled: true
            existingClaim: nextcloud-db-claim
      

      Hope it helps!

      source
    • x3i@kbin.social ⁨6⁩ ⁨months⁩ ago

      I think it was literally called "config". I will check my setup and provide the mount points I used here later today, if you back these up, it should work. Put some disposable data on it once you finished setup and then upgrade to a newer version to see if everything works. You can specify the image tag to use manually (or you install an older chart version).
      I also pinned the postgres version to 14, not sure if I can recommend that but I had issues with DB upgrades in a docker installation, so I tend to be careful there.

      source