Just wanted to share my happiness.

AIO is the new (at least on my timeline) installation method of Nextcloud, where most of the heavy-lifting is taken care of automatically.

https://github.com/nextcloud/all-in-one

    • vortexsurfer@lemmy.world
      link
      fedilink
      English
      arrow-up
      24
      ·
      10 months ago

      No, you give the AIO container access to your docker daemon and it will create / handle / supervise all the other containers nextcloud needs.

      • haplo@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        10 months ago

        I appreciate the simplicity, but giving such broad permissions makes me unease and the main reason why I’m putting off moving to Nextcloud AIO. Am I the only one who thinks like this?

      • genie@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        10 months ago

        Love me some docker compose! I switched from a manually built VM over to the AIO setup about a year ago and never looked back. It’s been rock solid for me and my ~10 users so far.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      10 months ago

      It containerizes all the subcomponents under a mastercontainer, and even has support for community containers of things like pihole, caddy and dlna. So you have image control over each component, as well as codespace separation.

      After 7 or 8 years of various forms of Nextcloud, I have to say this is the easiest one to maintain, upgrade and backup outside of my VM snapshots.

        • ikidd@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          10 months ago

          Not really, it just makes containers in your docker, accessible like any others. The mastercontainer can be used to control and update them, but you can just exec -dit them like any other containers you find in your docker ps