-
Notifications
You must be signed in to change notification settings - Fork 58
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
Log reader for Send, Earn and Sweep inside UI #748
Comments
Very valid reasoning. Thank you @editwentyone I think it might be a bit tricky, as we store api tokens in session storage and no other tab has access, afaik. However, it would be nice to have. |
Hi @editwentyone Can I work on this issue? |
Of course you can! However, I am afraid is indeed tricky since this is something JM does not provide out of the box. It would be better to have an api endpoint this data can be retrieved from. |
I've been looking into this for the past couple of days, and it's definitely a tricky implementation :) Would it make sense if I create an issue in joinmarket-clientserver to request a new API endpoint for streaming logs? |
I think it would help in the long run! happy that you are helping out :) dont ask for permission, just jump right into it and have fun |
As a user I would love to be able to open an external window with my current log streaming automatically what is happening in the background.
when I start earn I get the ID and can find the correct log on the node. but that needs ssh and tail -f running.
when I start a Send, I am blind because I can't pinpoint what log was created lastly to use easily.
behause there is always only one type of process running (send, earn, sweep) it should be easy to also show only the one correct log streaming
Describe the solution you'd like
JAM should give me a possibility to one click and open an a modal to see the correctly fetched log and give me opportunity to open that log even in its own external window to keep it open.
Describe alternatives you've considered
ssh into my node, find the right log that is active right now and stream that with tail -f
The text was updated successfully, but these errors were encountered: