Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync Issues #21

Closed
mark-prins opened this issue May 12, 2022 · 2 comments
Closed

Sync Issues #21

mark-prins opened this issue May 12, 2022 · 2 comments
Labels
Epic sync v5 relating to finishing off full sync v5 support
Milestone

Comments

@mark-prins
Copy link
Collaborator

Some sync tasks to finish up:

  • Make sure remote server backup don’t sync to live central. Hardware ID? Wondered about auto generating the h/w ID on the server rather than having the client specify it too.
  • Address caveats in V5 on central and remote. Andrei and Chris have been working on full spec for the whole V5 (including mSupply remote sites), when this spec is finalised we can identify the minimal changes that are needed for V1 release (scope of minimal changes = minimal for omSupply to work with current feature set, so doesn’t include new sync in mSupply).
  • Merge v5 Sync branch ( aiming for end of June )

Also note that the new branch would require 4D V19

@Chris-Petty
Copy link
Contributor

Said Sync v5 spec/design decisions evolving here https://github.com/sussol/msupply/pull/10750/

Majority involve 4D changes, but there'll be changes to remotes too.

@mark-prins mark-prins transferred this issue from another repository May 23, 2022
@mark-prins mark-prins added this to the Version 1 milestone May 23, 2022
@mark-prins mark-prins added v1 sync v5 relating to finishing off full sync v5 support labels Aug 1, 2022
@mark-prins
Copy link
Collaborator Author

I think that #156 has this one covered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic sync v5 relating to finishing off full sync v5 support
Projects
None yet
Development

No branches or pull requests

2 participants