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

    I’m still too container stupid to understand the right way to do this. I’m running it in docker under kubernetes and sometimes I don’t update nextcloud for a long time then I do a container update and it’s all fucked because of incompatible php versions of some shit.

    • recapitated@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 months ago

      I don’t remember much about how to use kubernetes but if you can specify a tag like nextcloud:28 instead of nextcloud:latest you should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.

      There are varying degrees of version specificity available: https://hub.docker.com/_/nextcloud/tags

      Make sure you’re periodically evaluating your site with https://scan.nextcloud.com/ and following all of the recommended best practices.

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

      Kubernetetes is crazy complex when comparing to docker-compose. It is built to solve scaling problems us self-hosters don’t have.

      First learn a few docker commands, set some environment variables, mount some volumes, publish a port. Then learn docker-compose.

      Tutorials are plenty, if those from docker.com still exist they’re likely still sufficient.