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

  • corsicanguppy@lemmy.caEnglish
    211·
    10 months ago

    curl -fsSL https://get.docker.com | sudo sh

    Jesus Ritchie Christ, can we de-normalize ‘run anonymous superscript as root’ bullshit? It’s dumb when Oracle does it, it’s dumb when SuSE does it. It’s dumb all the time.

  • cybersandwich@lemmy.worldEnglish
    17·
    10 months ago

    I could never get the AIO setup to work well for some reason. It was also a couple versions behind it seemed.

    I…uh…know it’s not popular on the fed, but I use the nextcloud snap package and it’s been rock solid. It’s always up -to-date and they have a backup/export feature too.

    • vortexsurfer@lemmy.worldEnglish
      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.worldEnglish
        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.worldEnglish
        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.worldEnglish
      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.worldEnglish
          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

  • Dyskolos@lemmy.zipEnglish
    12·
    10 months ago

    Didn’t knew it exists. That might make me give nextcloud another chance. Thanks man.

    • robber@lemmy.mlOPEnglish
      7·
      10 months ago

      Welcome. I use it in conjunction with Fedora CoreOS so I hopefully never have to manually update anything ever again.

      • twack@lemmy.worldEnglish
        5·
        10 months ago

        I was about to ask why this is better than the docker installation, but I see step one is to install docker haha.

        I’ve been running the docker container for a long time, it works very well. It is a bit more complicated if you try and use extensions that require seperatw containers (like setting up collabora), but that can be done as well. It’s just more complicated.

        I do remember needing to know how to access the internal terminal a few times, but I don’t remember why. If I think of it I’ll come back and add instructions.

        Edit: It’s to be able to run occ commands:

        Sudo docker exec -u www-data nextcloud-app php occ “Command goes here”

        Sudo docker exec -u www-data nextcloud-app php occ files:scan --all

        • ikidd@lemmy.worldEnglish
          2·
          10 months ago

          As a former self-configured docker compose NC user, I have to say I’m way happier with the AIO. But still, the older docker method was head and shoulders over any other method of running NC that I’d used.

        • robber@lemmy.mlOPEnglish
          2·
          10 months ago

          With AIO it’s almost the same: sudo docker exec -u www-data nextcloud-aio-nextcloud php occ

  • namelivia@lemmy.worldEnglish
    10·
    10 months ago

    I’m still using the self hosted docker image, the all in one is too bloated for me and my computing resources are quite limited. Why would I like an antivirus? Or a backup solution different than the one I use to backup the rest of my containers?

    Cool initiative anyway for other kind of users though.

    • robber@lemmy.mlOPEnglish
      2·
      10 months ago

      Running the AV container is optional, as is using the integrated backup solution. But I can see how that might feel bloated if you don’t need it.

  • rambos@lemmy.worldEnglish
    6·
    10 months ago

    One of the first services on my server was nextcloud in docker container from lsio. Never had problems so there was no need to try AIO, but so many people recommend that, it will be my next setup if this one fails me

    • robber@lemmy.mlOPEnglish
      3·
      10 months ago

      I decided to go with this one because it’s now the official distribution channel and supported by the devs. But the lsio one looks pretty solid as well.

  • PoopMonster@lemmy.worldEnglish
    6·
    10 months ago

    I wish I could’ve like next cloud more, but it seemed bloated as all hell and was slow regardless of what machine I tried running it on :(. I might give it another go one day.

    • robber@lemmy.mlOPEnglish
      5·
      10 months ago

      Nextcloud is a web-based, open-source cloud / collaboration software suite, which can be self-hosted