-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
NTFY: allow using custom server URL #137
Comments
Hi there 👋 You are using the free plan of the Create Issue Branch App. If you want to continue using this App, please upgrade to the Developer plan. If you have any questions reach out to me by opening an issue. |
Branch issue-137-NTFY_allow_using_custom_server_URL created! |
Try |
I'm actually trying to use the exception notify package, but sure |
Please try to configure <?php
declare(strict_types=1);
use Guanguans\LaravelExceptionNotify\Pipes\LimitLengthPipe;
return [
// ....
/**
* The default reported channels.
*/
'defaults' => env_explode('EXCEPTION_NOTIFY_DEFAULTS', [
'log',
'ntfy',
]),
// ...
/**
* The list of channels.
*/
'channels' => [
// ...
'ntfy' => [
'driver' => 'notify',
'authenticator' => [
'class' => \Guanguans\Notify\Foundation\Authenticators\NullAuthenticator::class,
// 'class' => \Guanguans\Notify\Ntfy\Authenticator::class,
// 'usernameOrToken' => env('EXCEPTION_NOTIFY_NTFY_USERNAMEORTOKEN', ''),
// 'password' => env('EXCEPTION_NOTIFY_NTFY_PASSWORD', ''),
],
'client' => [
'class' => \Guanguans\Notify\Ntfy\Client::class,
'http_options' => [
'base_uri' => 'your custom server uri.',
// ...
],
],
'message' => [
'class' => \Guanguans\Notify\Ntfy\Messages\Message::class,
'topic' => env('EXCEPTION_NOTIFY_NTFY_TOPIC', 'laravel-exception-notify'),
'title' => '{title}',
'message' => '{report}',
],
'pipes' => [
hydrate_pipe(LimitLengthPipe::class, 4096),
],
],
// ...
],
]; |
The ntfy.sh server URL is hardcoded in the
Guanguans\Notify\Ntfy\Client
class and it shoudn't be.I could extend the class, of course, but that's a lot of code to patch a single value.
The text was updated successfully, but these errors were encountered: