Comment on Plex Users Fear New Feature Will Leak Porn Habits to Their Friends and Family

• Kusimulkku@lemm.ee ⁨7⁩ ⁨months⁩ ago

  What do you mean? I don’t think there’s much at all of maintenance needed to be done.

  source

  • AtariDump@lemmy.world ⁨7⁩ ⁨months⁩ ago

    Updating.

    Saving data outside containers so that updates don’t hose said data.

    Only updating one project’s container at a time and not all of them.

    Backing up data.

    source

    • Kusimulkku@lemm.ee ⁨7⁩ ⁨months⁩ ago

      I’ve never had issues with their data. Logs, configs or media. Just set up the volumes and you’re done afaik.

      Updating single container can be done with a simple pull and recreate or with compose by having a single docker thing on that particular compose file. Not that I’ve chosen to do that, many services are simpler since a lot of them work together anyway.

      Backing up should be as easy as backing up anything. Put all your docker configs in the same location, save the compose file(s), check that the paths are same in new system and you’ll be up and running.

      source

      • AtariDump@lemmy.world ⁨7⁩ ⁨months⁩ ago

        It’s tough when the directions leave out making a folder outside of the container to store configs. That’s burned me once.

        I’m not looking to update a single container but a single project’s container; just because I want to update project A’s containers doesn’t mean I also want to update project B’a containers. The only instructions I’ve found update all projects at the same time.

        I’m not so worried about the config files as I am worried about backing up the data inside the containers being created from data outside the containers.

        source

        • -> View More Comments