grehund@beehaw.org to Technology@beehaw.org · 1 year ago"Lemmy Explorer" a new website to explore Lemmy communities and instanceslemmyverse.netexternal-linkmessage-square74fedilinkarrow-up1414arrow-down10file-textcross-posted to: youshouldknow@lemmy.worldfediverse@lemmy.worldfediverse@kbin.socialsupport@beehaw.orglemmyworld@lemmy.worldnewcommunities@lemmy.worldfreemediaheckyeah@lemmy.fmhy.mlgeneral@lemmy.cafetechnology@lemmy.ml
arrow-up1414arrow-down1external-link"Lemmy Explorer" a new website to explore Lemmy communities and instanceslemmyverse.netgrehund@beehaw.org to Technology@beehaw.org · 1 year agomessage-square74fedilinkfile-textcross-posted to: youshouldknow@lemmy.worldfediverse@lemmy.worldfediverse@kbin.socialsupport@beehaw.orglemmyworld@lemmy.worldnewcommunities@lemmy.worldfreemediaheckyeah@lemmy.fmhy.mlgeneral@lemmy.cafetechnology@lemmy.ml
minus-squarexavier666@lemm.eelinkfedilinkarrow-up2·edit-21 year agoIf 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
If the instance is setup as a docker container, then it should be easy. The following should be transferred
At the destination, the docker volume dirs should be unzipped and the new paths should be updated in the docker-compose file