With this SeAT Package you can setup and manage notifications. It is build to be expended from within the package or from another package. Please read more about it further down.
Important: seat-notifications are work in progress and certainly have some bugs please do report any findings to seat-slack and report it as an issue.
- cd to
/var/www/seat
- enter
composer require herpaderpaldent/seat-notifications
- run migration
php artisan migrate
To enable seat-notifications
functionality of sending notifications. Create a bot for your notification channel. By default seat-notifications offers two notification channels which could be extended by other packages: slack
and discord
:
a more detailed guide on oAuth creation will follow for now the blow table must suffice:
Notification Channel | Redirect URLs | Comment |
---|---|---|
Discord | {seat_url}/seatnotifications/discord/configuration/callback/server | This callback url is needed for the configuration of your discord bot. |
Discord | {seat_url}/seatnotifications/discord/callback/user | This callback url is needed for the authentication of a discord user. |
Slack | {seat_url}/seatnotifications/slack/configuration/callback/server | This callback url is needed for the configuration of your slack bot. |
Slack | {seat_url}/seatnotifications/slack/callback/user | This callback url is needed for the authentication of a slack user. |
Note: you may only configure one notification channel at your will. However, for discord you must create a bot in your application. For Slack you need to add the bot permission to your oauth scope.
To be able to subscribe to a notification the user needs the appropriate permission. Please setup a role that carries the needed permission and assign it to users that should be able to receive the notification.
Since the notifications are send out by your workers you need to restart them to pick up the new code. Do this either via docker-compose restart seat-worker
if you use docker, or supervisorctl restart worker
on linux distributions.
Users need to authenticate for your setup notification channel prior to receiving notifications. they may do this in the registration box on the notification page.
- Send
RefreshTokenDeleted
Notification to Discord and/or Slack when arefresh_token
is deleted. - Using Model Observer to dispatch Notifications
- Notifications are queueable and send out via the queue.
- The RefreshTokenNotification is able to be delivered to Channels or via DM on the users preference.
Most importantly: take note of laravel's notification documentation. Secondly have a look at this package service provider as it helps with merging the services array properly. The provided example of RefreshTokenDeletedNotification is based upon it. Notifications are being send by using the Notification
facade:
Notification::send($receipients, (new RefreshTokenDeletedNotification($refresh_token)));
where $receipients
are a collection of modal that should receive the notification and $refresh_token
is the deleted refresh_token
that is passed to the constructor. In this example we use an Observer to send notifications: Observer.
If you have written a new notification driver that you would like to use for sending notifications to your users you might extend config/services.php
similar to the provided example:
'seat-notification-channel' => [
'discord' => Herpaderpaldent\Seat\SeatNotifications\Drivers\DiscordNotificationDriver::class,
],
Your driver should extend Herpaderpaldent\Seat\SeatNotifications\Drivers\AbstractNotificationDriver
and should contain;
/**
* The view name which will be used to store the channel settings.
*
* @return string
*/
public static function getSettingsView() : string;
/**
* The label which will be applied to the subscription button.
*
* @return string
*/
public static function getButtonLabel() : string;
/**
* The CSS class which have to be append into the subscription button.
*
* @return string
*/
public static function getButtonIconClass() : string;
/**
* @return array
*/
public static function getChannels() : array;
/**
* Determine if a channel has been properly setup.
*
* @return bool
*/
public static function isSetup(): bool;
If you want to extend the available notifications you need to extend the seat-notification
array in config/services.php
:
'seat-notification' => [
// notification => [provider => implementation]
Herpaderpaldent\Seat\SeatNotifications\Notifications\RefreshToken\AbstractRefreshTokenNotification::class => [
'discord' => Herpaderpaldent\Seat\SeatNotifications\Notifications\RefreshToken\DiscordRefreshTokenNotification::class,
'slack' => Herpaderpaldent\Seat\SeatNotifications\Notifications\RefreshToken\SlackRefreshTokenNotification::class,
],
Your abstract notification must extend Herpaderpaldent\Seat\SeatNotifications\Notifications\AbstractNotification
and contain the following methods to add your notification to the users notification list:
/**
* Return a title for the notification which will be displayed in UI notification list.
* @return string
*/
public static function getTitle(): string;
/**
* Return a description for the notification which will be displayed in UI notification list.
* @return string
*/
public static function getDescription(): string;
/**
* Determine if a notification can target public channel (forum category, chat, etc...).
* @return bool
*/
public static function isPublic(): bool;
/**
* Determine if a notification can target personal channel (private message, e-mail, etc...).
* @return bool
*/
public static function isPersonal(): bool;
/**
* Determine the permission needed to represent driver buttons.
* @return string
*/
public static function getPermission(): string;
In order to dispatch notification solely to receiver that subscribed to the notification it is advised to use a custom dispatcher job f.e.:
public function handle()
{
Redis::funnel('soft_delete:refresh_token_' . $this->refresh_token->user->id)->limit(1)->then(function () {
logger()->info('SoftDelete detected of ' . $this->refresh_token->user->name);
$recipients = NotificationRecipient::all()
->filter(function ($recipient) {
return $recipient->shouldReceive(AbstractRefreshTokenNotification::class);
});
if($recipients->isEmpty()){
logger()->debug('No Receiver found for this Notification. This job is going to be deleted.');
$this->delete();
}
$recipients->groupBy('driver')
->each(function ($grouped_recipients) {
$driver = (string) $grouped_recipients->first()->driver;
$notification_class = AbstractRefreshTokenNotification::getDriverImplementation($driver);
Notification::send($grouped_recipients, (new $notification_class($this->refresh_token)));
});
}, function () {
logger()->debug('A Soft-Delete job is already running for ' . $this->refresh_token->user->name);
$this->delete();
});
}