fenos / Notifynder by slypver3

Management system of internal notifications for Laravel 5.*
202,171
432
20
notifications laravel
Github Link
Packagist Link
Package Data
Maintainer Username: slypver3
Maintainer Contact: fabri_feno@yahoo.it (Fabrizio Fenoglio)
Package Create Date: 2014-04-04
Package Last Update: 2019-01-15
Home Page:
Language: PHP
License: MIT
Last Refreshed: 2024-11-09 15:02:27
Package Statistics
Total Downloads: 202,171
Monthly Downloads: 174
Daily Downloads: 1
Total Stars: 432
Total Watchers: 20
Total Forks: 86
Total Open Issues: 5

Notifynder 4 - Laravel 5

GitHub release GitHub license GitHub issues Total Downloads VersionEye SensioLabs Insight

Travis branch StyleCI Scrutinizer Build

Scrutinizer Code Quality Code Climate Coveralls

Slack Team Slack join

Notifynder is designed to manage notifications in a powerful and easy way. With the flexibility that Notifynder offer, It provide a complete API to work with your notifications, such as storing, retrieving, and organise your codebase to handle hundreds of notifications. You get started in a couple of minutes to "enable" notifications in your Laravel Project.

Compatible DBs: MySQL - PostgreSQL - SQLite

Documentation: Notifynder Docu

Installation

Step 1

Add it on your composer.json

"fenos/notifynder": "^4.0"

and run

composer update

or run

composer require fenos/notifynder

Step 2

Add the following string to config/app.php

Providers array:

Fenos\Notifynder\NotifynderServiceProvider::class,

Aliases array:

'Notifynder' => Fenos\Notifynder\Facades\Notifynder::class,

Step 3

Migration & Config

Publish the migration as well as the configuration of notifynder with the following command:

php artisan vendor:publish --provider="Fenos\Notifynder\NotifynderServiceProvider"

Run the migration

php artisan migrate

Senders

A list of official supported custom senders is in the Notifynder Doc.

We also have a collect issue for all additional senders we plan or already have.

If you want any more senders or want to provide your own please create an issue.

ToDo

Tasks we still have to do:

  • add unittests for parser and models
  • complete the new documentation

Versioning

Starting with v4.0.0 we are following the Semantic Versioning Standard.

Summary

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release (alpha, beta, rc) are available as extensions to the MAJOR.MINOR.PATCH format.

Contributors

Thanks for everyone who contributed to Notifynder and a special thanks for the most active contributors

Services