• bigb@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    1 day ago

    Here is a migration guide from the devs: https://docs.seerr.dev/migration-guide

    How did you install Overseerr in CasaOS?

    If I understand it, Docker users just need to update the compose file and the settings should migrate. But I haven’t done this yet and I’ll definitely be backing up first.

    • oong3Eepa1ae1tahJozoosuu@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      It’s more than that, you have to make sure a certain directory is owned by the “node” user and it has to have uid 1000. That’s a small but very important step in said migration guide, which I overlooked initially. Nothing happened though, container wouldn’t start and its logs kept pointing to this directory, then I saw it in the docs.

    • Jediwan@lemy.lolOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      1 day ago

      CasaOS is like a frontend for Docker, it has an “app store” where it’s just a handful of clicks to install something.

      Anyway, I did see that guide but the steps for Docker just say “Refer to Seerr Docker Documentation” which is well, kind of complicated.

      I do have Portainer and know my way around it’s basics if it makes it easier.

      • Black616Angel@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 hours ago

        If you have portainer, it should be relatively easy.

        First make a backup of the old config folder (I just copied mine to a new seerr folder) then you insert your current data into the docker compose-file they show at your link and import that as a stack. Boom, done.

        If you have an existing stack with, let’s say, radarr and sonarr and plesk and overseerr, then you can backup the old compose file, and replace only the overseer part with the code from the given compose config.