github.com/cozy/cozy-stack@v0.0.0-20240603063001-31110fa4cae1/docs/archives/moving.md (about)

     1  [Table of contents](../README.md#table-of-contents)
     2  
     3  This document was written in october 2016.
     4  
     5  # Moving
     6  
     7  This document is a stub to hold information about moving one's cozy from an
     8  hosting provider to another.
     9  
    10  We do moving by exporting data to a tarball, and then importing the tarball. The
    11  files inside the tarball should be organized in a documented way, and with
    12  standard formats, to open interoperability with cloud solutions.
    13  
    14  You also have DNS and TLS certificates to change
    15  
    16  Once we start doing some intercozy communication, we might have issues with the
    17  transition period.
    18  
    19  -   I export my "bob.cozycloud.cc" from host1 as a tarball
    20  -   My friend A's cozy send me an update notification the message gets to host1
    21  -   I trigger DNS change
    22  -   My friend B's cozy send me something, its DNS is not up-to-date, the message
    23      gets to host1
    24  -   DNS change is complete, all further messages will reach host2
    25  
    26  The sharing protocol have to take into account the fact that a cozy can have
    27  accepted a message, but then forget about it (better, as it also covers the
    28  crash case).