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
fix: autopeering - use localtunnel #2633
Conversation
✅ Deploy Preview for brilliant-pasca-3e80ec ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I was able to send a payment from local env -> rafiki.money, but like you mention in the description, not the other way around. |
packages/documentation/src/content/docs/playground/autopeering.md
Outdated
Show resolved
Hide resolved
packages/documentation/src/content/docs/playground/autopeering.md
Outdated
Show resolved
Hide resolved
packages/documentation/src/content/docs/playground/autopeering.md
Outdated
Show resolved
Hide resolved
I'm not sure I follow |
@sabineschaller When we are approving the grant request in rafiki.money, I think it would be better to use the grant initiation flow with the |
But what would that page be? |
@sabineschaller yeah I think I confused myself there 😅 , this is from bruno |
Changes proposed in this pull request
I only swap out tunnelmole and now use localtunnel. The additional interaction is only required when accessing the localtunnel url through the browser. Hence, our API requests work fine.
Right now, the localtunnel "login" screen is shown when going through the consent flow. We could get around even that when we make the Rafiki.money user the sender and the local user the receiver. However, since Rafiki.money is not on the latest version of Rafiki, the polling interaction flow does not work yet.
Context
Even though it's not the same, it
Checklist
fixes #number