Not mine, just cross-posting.

  • xavier666@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    A one-click account transfer to a different instance would be great. However, there can be several “gotchas”, maybe the target instance has lower “permissions”, so that can lead to data loss. Eg: my instance doesn’t allow pictures more than 100 kb, some other instance doesn’t allow creation of communities. So this needs to be carefully throughout.

    • roboTRASH@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Seems the easiest solution to that would be to simply have a comparison view. The permissions are setup using some sort of standardized method, yes? Config file, GUI (which just alters config file), whatever. Certainly it wouldn’t be hard to simply grab and organize a list of perms from both instances and toss em up side by side. Could even add notes (i.e. if photo storage on Instance A > Instance B notify user that “migrating to this instance may cause some larger photos to be removed from your account”).

      I’m not a professional programmer (sys admin, so mostly just automation) but there are certainly solutions to this.

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      oh I was thinking a full instance backup. As an instance admin it’d be nice to backup the whole thing in a standardized way so someone else could grab it and spin it up if I collapsed tomorrow, all the community and users

      • xavier666@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        If the instance is setup as a docker container, then it should be easy. The following should be transferred

        • docker-compose file
        • zipped up volume directory

        At the destination, the docker volume dirs should be unzipped and the new paths should be updated in the docker-compose file