Notifications allow you to inform the user about a state changes in your application.
The Laravel notifications supports sending notifications across a variety channels (mail, SMS, Slack, Database...).
When using the Database channel the notifications will be stored in a database to be displayed in your client interface.
For more details refer to this link.
Containers MAY or MAY NOT have one or more Notification.
Ship may contain Application general Notifications.
- All Notifications MUST extend from
Example: a simple Notification
Usage from an Action or Task:
Notifications can be sent from Actions or Tasks using the
Alternatively you can use the
Illuminate\Notifications\Notifiable trait on the notifiable object "e.g. User" and then call it as follows:
To select a notification channel, apiato have the
app/Ship/Configs/notification.php config file where you can define the array of supported channels "e.g. SMS, Email, WebPush...", to be used for all your notifications.
If you want to override the configuration for some notifications classes, or if you prefer to define the channels within each notification class itself,
you can override the via function
public function via($notifiable) in the notification class and define your channels.
Checkout laravel notification channels for list of supported integrations.
To queue a notification you should use
Illuminate\Bus\Queueable and implement
Generally you need to generate the notification migration
php artisan notifications:table, then run
php artisan migrate,
however just running the migration command will do the job, since Apiato already adds the
_create_notifications_table.php in the default migrations files directory