We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We will have several WebHooks available with Mercurius.
List of WebHooks (WIP):
MessageSent
UserGoesActive
UserGoesInactive
UserStatusChanged
For saving WebHooks information, maybe we can use config/mercurius?
config/mercurius
Example for config:
/* |-------------------------------------------------------------------------- | WebHooks |-------------------------------------------------------------------------- | | You may specify the WebHooks information, the URL address receiving the | HTTP POST callbacks, the Secret Token and the list of WebHooks to use. | */ 'webhooks' => [ 'url' => 'https://myappdomain.com', 'secret_token' => env('MERCURIUS_WEBHOOKS_TOKEN', false), 'events' => [ 'MessageSent' => false, 'UserGoesActive' => false, 'UserGoesInactive' => false, 'UserStatusChanged' => false, ], ],
Maybe, having a command to generate the MERCURIUS_WEBHOOKS_TOKEN to ease this process?
MERCURIUS_WEBHOOKS_TOKEN
Please send your feedback. TY!
Ping: @marktopper
The text was updated successfully, but these errors were encountered:
These could also be Broadcast events too..
Sorry, something went wrong.
Hey @Braunson, you can expect Broadcast Events, this will be released soon with #12 Broadcast User Status.
As for the WebHooks, @marktopper have another idea for the config, which is more flexible supporting custom settings per endpoint:
/* |-------------------------------------------------------------------------- | WebHooks |-------------------------------------------------------------------------- | | You may specify the WebHooks information, the URL address receiving the | HTTP POST callbacks, the Secret Token and the list of WebHooks to use. | */ 'webhooks' => [ [ 'endpoint' => 'https://domain.com/script.php', 'token' => env('MERCURIUS_TOKEN'), 'events': [ Launcher\Mercius\Events\MessageSent::class, Launcher\Mercius\Events\UserGoesActive::class, ] ], [ 'endpoint' => 'https://domain2.com/script.php', 'token' => env('MERCURIUS_TOKEN'), 'events': [ Launcher\Mercius\Events\MessageSent::class, ] ] ],
Thanks for your feedback, fell free to join us on Slack.
akazorg
marktopper
No branches or pull requests
We will have several WebHooks available with Mercurius.
List of WebHooks (WIP):
MessageSent
» Message ($id, $sender, $message, $date)UserGoesActive
» UserUserGoesInactive
» UserUserStatusChanged
» UserFor saving WebHooks information, maybe we can use
config/mercurius
?Example for config:
Maybe, having a command to generate the
MERCURIUS_WEBHOOKS_TOKEN
to ease this process?Please send your feedback. TY!
Ping: @marktopper
The text was updated successfully, but these errors were encountered: