Skip to content

How do migrations work? #68

Open
Open
@r5h

Description

@r5h

I've been reading the automerge doc section on migrations, and frankly it's a bit terrifying. As the (AFAICT) largest repo using of automerge, how do you guys handle changing the schema?

The simplest approach (with a single authoritative server serving both code and data) I can imagine is disallowing sync after a code update until the client has migrated it's local data to match the single sync server's version. Is something like that easy to do with automerge?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions