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

Migration from the original heartbeat #1

Open
lmaotrigine opened this issue Nov 1, 2023 · 2 comments
Open

Migration from the original heartbeat #1

lmaotrigine opened this issue Nov 1, 2023 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@lmaotrigine
Copy link
Member

Since this version makes some incompatible changes to the API and the internal storage model, a bit of work is necessary to migrate statistics and device and beat history from an existing server.

An implementation would involve

  • Reading a dump.rdb and parsing out JSON, or require that a redis server be running
  • Migrate devices to the new format using POST /api/devices and communicate the resulting tokens to the user.
  • Migrate beat history ensuring foreign key constraints aren't violated.

cc @5HT2 since you wanted to take this up.

@lmaotrigine lmaotrigine added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Nov 1, 2023
@lmaotrigine
Copy link
Member Author

Today was a particularly dull day so I put this together in about 30 minutes. Feedback welcome.

@5HT2
Copy link
Member

5HT2 commented Nov 21, 2023

hey there, thanks for the ping + migration tool to look at c:
i was a lil busy recently, i'll review this tmrw most likely! tyvm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants