PHPackages                             zofe/ticket-module - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. zofe/ticket-module

ActiveRapyd-module[Utility &amp; Helpers](/categories/utility)

zofe/ticket-module
==================

ticket module for rapyd-livewire application

0.0.2(3y ago)131mitPHPPHP ^8.0|^8.1|^8.2

Since Mar 25Pushed 3y ago1 watchersCompare

[ Source](https://github.com/zofe/ticket-module)[ Packagist](https://packagist.org/packages/zofe/ticket-module)[ RSS](/packages/zofe-ticket-module/feed)WikiDiscussions main Synced yesterday

READMEChangelogDependencies (15)Versions (3)Used By (0)

Ticket Module
=============

[](#ticket-module)

This is a Ticket module for a Laravel application (&gt;= 8)

it use layout module and auth module.

Installation &amp; configuration
================================

[](#installation--configuration)

Your can require this module in your laravel application using:

```
composer require zofe/ticket-module

php artisan migrate

```

create a configuration file "ticket.php" in your config folder and customize :

```
    'operators_roles'=>['admin'],
    'notification_email' => 'notification@email.it',

```

then add roles/permissions in the auth.php configuration file :

By default, tickets can be created by "user" (role) users and managed by "admin" (role) users. A minimal configuration for your config/auth.php file is:

```
'role_permissions' => [
        'admin' => [
            'view tickets', 'edit tickets',
        ],
        'user' => [
            'view own tickets', 'edit own tickets',
        ],
]

```

then you can seed some default data using:

```
php artisan db:seed --class="App\\Modules\\Ticket\\Database\\Seeders\\TicketCategories"

```

Layout
======

[](#layout)

Note that this module will install/use layout-module, you may need to do:

```
cd app/Modules/Layout/

npm i
npm run dev

```

this will compile scss and copy css assets to your public project folder

Charts
======

[](#charts)

this module use livewire charts, so you need to publish some assets:

```
php artisan vendor:publish --tag=livewire-charts:public
```

if you customize your layout make sure you include this directive

```
@livewireChartsScripts

```

Customizing Module
==================

[](#customizing-module)

To customize the module code, we recommend forking the original package repository on GitHub and making changes there. This way, you can maintain a separate branch for your changes, while also keeping up-to-date with the latest releases of the package.

To install your forked version of the package in your Laravel application, you can reference your forked repository in the composer.json file of your Laravel application using the "vcs" package type. Here's an example of what you can add to your composer.json:

```
"repositories": [
    {
        "type": "vcs",
        "url": "https://github.com//"
    }
],
```

Replace `` with your GitHub username and `` with the name of your forked package repository.

After adding your forked repository to composer.json, you can require your customized package in the same way you would require the original package:

```
composer require /:dev-
```

Replace ``, ``, and `` with the appropriate values for your forked repository and branch.

By using this approach, you can easily customize the module code while also keeping your code up-to-date with the latest releases of the package.

We encourage developers to make changes that could be useful to the wider community and contribute back to the original package repository via pull requests. This can help improve the package for everyone and ensure that your changes are integrated with the latest releases of the package.

###  Health Score

23

—

LowBetter than 26% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~12 days

Total

2

Last Release

1184d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/261951?v=4)[Felice Ostuni](/maintainers/zofe)[@zofe](https://github.com/zofe)

###  Code Quality

TestsPHPUnit

Static AnalysisPsalm

Type Coverage Yes

### Embed Badge

![Health badge](/badges/zofe-ticket-module/health.svg)

```
[![Health](https://phpackages.com/badges/zofe-ticket-module/health.svg)](https://phpackages.com/packages/zofe-ticket-module)
```

###  Alternatives

[psalm/plugin-laravel

Psalm plugin for Laravel

3355.3M346](/packages/psalm-plugin-laravel)[laravel/pulse

Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application.

1.7k15.1M132](/packages/laravel-pulse)[tallstackui/tallstackui

TallStackUI is a powerful suite of Blade components that elevate your workflow of Livewire applications.

725173.2k14](/packages/tallstackui-tallstackui)[propaganistas/laravel-disposable-email

Disposable email validator

6023.0M7](/packages/propaganistas-laravel-disposable-email)[api-platform/laravel

API Platform support for Laravel

58171.6k14](/packages/api-platform-laravel)[filament/support

Core helper methods and foundation code for all Filament packages.

2331.0M245](/packages/filament-support)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
