Download the PHP package nawasara/notification without Composer
On this page you can find all versions of the php package nawasara/notification. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?
Informations about the package notification
Nawasara Notification
Unified outbound notification for the Nawasara superapp framework. Build a Blade template once, then send it to anyone over any registered channel via a single fluent API. Every send is queued, retried with backoff on failure, and recorded in an audit log.
Features
Notifyfacade — fluent, chainable:Notify::to($user)->template('ssl.expiry')->data([...])->send()- Email channel (MVP) — sends via Laravel's Mail facade. Credentials read from the
smtpVault group with a fallback to.env(MAIL_*) - Template manager — Blade-rendered subject and body, multi-channel bodies (HTML / text / WhatsApp / Telegram / in-app), priority and active flag
- Live preview — render any template against arbitrary JSON variables in an iframe before saving
- Test send — kick off a real send to your own email from the template list to verify rendering and delivery end-to-end
- Audit log — every send is one row in
nawasara_notification_logswith status (queued / sending / sent / delivered / failed / bounced), error trace, attempts, and rendered body - Retry from UI — failed and bounced logs can be re-dispatched in one click
- Future channels — WhatsApp, Telegram, and in-app are stubbed in the schema and contract; only
EmailChannelis implemented in the MVP
Installation
Auto-discovered. The Notify facade is registered as an alias.
SMTP credentials
The package reads SMTP credentials from the smtp Vault group at send time. Open /nawasara-vault/credentials → SMTP Email → fill in:
| Field | Example |
|---|---|
| Host | smtp.gmail.com |
| Port | 587 |
| Encryption | tls |
| Username | [email protected] |
| Password | (Gmail app password if 2FA is on) |
| From Address | [email protected] |
| From Name | Nawasara Kominfo |
Use Test Connection in the dropdown to verify the host is reachable. If Vault is empty, the channel falls back to whatever Laravel resolves from .env — useful in local where MAIL_MAILER=log writes the rendered email to storage/logs/laravel.log.
Sending notifications
Template-driven
Ad-hoc
Synchronous (skip queue)
Useful for tests and admin actions that need immediate feedback:
Pages
| Route | Permission |
|---|---|
/nawasara-notification/templates |
notification.template.view |
/nawasara-notification/logs |
notification.log.view |
Permissions
| Permission | Description |
|---|---|
notification.template.view |
View template list |
notification.template.create |
Create template |
notification.template.update |
Update template |
notification.template.delete |
Delete template |
notification.log.view |
View notification log |
notification.log.retry |
Retry a failed/bounced notification |
notification.test.send |
Trigger a Test Send from the template UI |
notification.broadcast.send |
Broadcast (planned for future) |
Roadmap
- WhatsApp channel via
nawasara/whatsapp-forwarder - Telegram bot channel
- In-app notification bell in topbar
- Webhook delivery callbacks (open/click tracking, bounce handling)
- User notification preferences (per-channel, quiet hours)
- Template broadcast (blast to role / OPD / custom audience)
See docs/todo-notification.md for the full plan.
Author
Pringgo J. Saputro <[email protected]>
License
MIT
All versions of notification with dependencies
PHP Build Version
Package Version
Requires
php Version
^8.1
illuminate/support Version ^10.0|^12.0
spatie/laravel-permission Version ^6.0
nawasara/ui Version *
nawasara/sync Version *
nawasara/vault Version *
livewire/livewire Version ^3.0
illuminate/support Version ^10.0|^12.0
spatie/laravel-permission Version ^6.0
nawasara/ui Version *
nawasara/sync Version *
nawasara/vault Version *
livewire/livewire Version ^3.0
The package nawasara/notification contains the following files
Loading the files please wait ...