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

Look into ngrok alternatives and configuration #193

Open
IanMitchell opened this issue Oct 16, 2022 · 1 comment
Open

Look into ngrok alternatives and configuration #193

IanMitchell opened this issue Oct 16, 2022 · 1 comment
Labels
Feature New things ✨

Comments

@IanMitchell
Copy link
Owner

Not everyone will want to use ngrok, some will have premium, etc - we should look into ways of accommodating them.

@IanMitchell IanMitchell added the Feature New things ✨ label Oct 16, 2022
@IanMitchell IanMitchell added this to the Interaction Kit v1.1 milestone Oct 16, 2022
@Stalruth
Copy link
Contributor

Stalruth commented Oct 19, 2022

Something like this could potentially work as an option; sending responses over the REST API in dev (after receiving them over the Gateway) means you get actual error messages.

This wouldn't work for any bot without a Bot User, but Interaction Kit already pushes users to make a Bot User so maybe not an issue?

EDIT: the script essentially takes a token, URL (probably localhost) and port and forwards Interactions received on the Gateway to that host - some extra config on the bot's end with keys is required too which is a bit of a pain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New things ✨
Projects
None yet
Development

No branches or pull requests

2 participants