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

Update rmapi to v0.0.25 #21

Merged
merged 3 commits into from
Jan 3, 2023
Merged

Update rmapi to v0.0.25 #21

merged 3 commits into from
Jan 3, 2023

Conversation

nov1n
Copy link
Owner

@nov1n nov1n commented Dec 23, 2022

  • Fixes the issue authenticating to the Remarkable API.
  • Speeds up building the document tree on startup.
  • Adds a script to automate updating rmapi binaries.

@vincentclaes
Copy link

This seems to work 🥳

cd ~
rm -rf .rmapi-cache
rm .rmapi
rm .remarkable-pocket


 touch ~/.remarkable-pocket ~/.rmapi && mkdir -p ~/.rmapi-cache && docker run -it --env TZ=Europe/Amsterdam -p 65112:65112 -v ~/.remarkable-pocket:/root/.remarkable-pocket -v ~/.rmapi:/root/.rmapi -v ~/.rmapi-cache:/root/.cache/rmapi ghcr.io/nov1n/remarkable-pocket:0.4.0 -v

@nov1n
Copy link
Owner Author

nov1n commented Dec 31, 2022

Please be careful running this with software version 3.x. During my testing, I encountered some strange behavior, which is why I haven't merged this PR yet.

As stated above: use at your own risk.

@vincentclaes
Copy link

Please be careful running this with software version 3.x. During my testing, I encountered some strange behavior, which is why I haven't merged this PR yet.

As stated above: use at your own risk.

yep, but it seems to work on my end :)
Bought you a coffee! thanks a lot for making this. You should make a micro saas out of this!

@nov1n
Copy link
Owner Author

nov1n commented Dec 31, 2022

I'm glad you find it useful and thanks for the coffee. Much appreciated! (:

@nov1n nov1n changed the title Update rmapi to v0.0.23 Update rmapi to v0.0.25 Jan 3, 2023
@nov1n
Copy link
Owner Author

nov1n commented Jan 3, 2023

rmapi v0.0.25 fixed the problems that I observed. You might want to pull the new 0.0.4 and run that instead just to be sure!

@nov1n nov1n merged commit 19423d8 into main Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

failed to create a new device token Error on start-up
2 participants