After months of waiting, I finally got myself an instance with Libre Cloud. I was expecting basic file storage with a few goodies but boy, this is soooo much more. I am amaze by how complete this is!!! Apps let me configure my instance to fit everything I need, my workflow is now crazy fast and I can finally say goodbye to gdrive, gsuite, trello, calendar, etc. All of this, with 1tb while not giving any of ma data to some evil business for… 10$ cad a month!? Can’t believe this is not what every organisation are using.

  • stuckgum@lemmy.mlEnglish
    15·
    7 months ago

    Really a pain in the ass to set up and tweak to your liking. After you overcome that hurdle, it runs relatively good.

    • ksp [il/lui]@jlai.luEnglish
      6·
      7 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.

        • ksp [il/lui]@jlai.luEnglish
          1·
          7 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

      • hperrin@lemmy.worldEnglish
        3·
        7 months ago

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

        sudo apt install docker.io docker-compose

        • Norah - She/TheyEnglish
          5·
          7 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.

    • x3i@kbin.social
      3·
      7 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.

        • x3i@kbin.social
          1·
          7 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.

        • x3i@kbin.social
          1·
          7 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!