PHPackages bambolee-digital/event-user-manager - 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. [Authentication & Authorization](/categories/authentication) 4. / 5. bambolee-digital/event-user-manager ActiveLibrary[Authentication & Authorization](/categories/authentication) bambolee-digital/event-user-manager =================================== A user event management system for Laravel and FilamentPhp 1.0.1(1y ago)017MITPHPPHP ^8.1 Since Sep 15Pushed 1y ago1 watchersCompare [ Source](https://github.com/Bambolee-Digital/event-user-manager)[ Packagist](https://packagist.org/packages/bambolee-digital/event-user-manager)[ RSS](/packages/bambolee-digital-event-user-manager/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (3)Dependencies (3)Versions (3)Used By (0) Event User Manager ================== [](#event-user-manager) [Português](#gerenciador-de-eventos-de-usu%C3%A1rio) Event User Manager is a Laravel package for managing user events with support for recurrence, attachments, and integration with Filament for administration. Installation ------------ [](#installation) You can install the package via composer: ``` composer require bambolee-digital/event-user-manager ``` This package depends on spatie/laravel-translatable. If you haven't already installed it, you can do so by running: ``` composer require spatie/laravel-translatable ``` Configuration ------------- [](#configuration) Publish the configuration file with: ``` php artisan vendor:publish --provider="BamboleeDigital\EventUserManager\EventUserManagerServiceProvider" --tag="config" ``` This will create a `config/event-user-manager.php` file. You can modify the settings as needed. You will need to register the following resources in your filament configuration file: ``` use BamboleeDigital\EventUserManager\Filament\Resources\EventResource; use BamboleeDigital\EventUserManager\Filament\Resources\EventTypeResource; use BamboleeDigital\OnboardingPackage\Filament\Resources\QuestionResource; ->resources([ EventResource::class, EventTypeResource::class, RecurrencePatternResource::class, ]) ``` Usage ----- [](#usage) ### API [](#api) The package provides API endpoints for managing events, notes, attachments, and images. The main endpoints are: #### Events [](#events) - `GET /api/events`: List events - `POST /api/events`: Create a new event - `GET /api/events/{id}`: Get event details - `PUT /api/events/{id}`: Update an event - `DELETE /api/events/{id}`: Delete an event - `GET /api/events/past`: Get past events - `GET /api/events/future`: Get future events - `GET /api/events/status/{status}`: Get events by status #### Notes [](#notes) - `POST /api/events/{event}/notes`: Add a note to an event - `PUT /api/events/{event}/notes/{note}`: Update a note - `DELETE /api/events/{event}/notes/{note}`: Delete a note #### Attachments and Images [](#attachments-and-images) - `POST /api/events/{event}/attachments`: Add an attachment to an event - `DELETE /api/events/{event}/attachments/{attachment}`: Remove an attachment from an event - `POST /api/events/{event}/images`: Add an image to an event - `DELETE /api/events/{event}/images/{image}`: Remove an image from an event API Usage Examples ================== [](#api-usage-examples) Here are comprehensive examples for using the Event User Manager API. These examples use the Guzzle HTTP client, but you can adapt them to your preferred HTTP client. Setup ----- [](#setup) First, set up the HTTP client: ``` use GuzzleHttp\Client; $client = new Client([ 'base_uri' => 'http://your-api-base-url/', 'headers' => [ 'Authorization' => 'Bearer YOUR_API_TOKEN', 'Accept' => 'application/json', ], ]); ``` Events ------ [](#events-1) ### List Events [](#list-events) ``` $response = $client->get('api/events'); $events = json_decode($response->getBody(), true); ``` ### Create a Comprehensive Event [](#create-a-comprehensive-event) ``` $multipart = [ ['name' => 'name', 'contents' => 'Annual Company Retreat'], ['name' => 'description', 'contents' => 'Our yearly company-wide retreat for team building and strategy planning.'], ['name' => 'event_type_id', 'contents' => '1'], ['name' => 'start_date', 'contents' => '2024-07-15 09:00:00'], ['name' => 'end_date', 'contents' => '2024-07-17 17:00:00'], ['name' => 'status', 'contents' => 'active'], ['name' => 'recurrence_pattern_id', 'contents' => '2'], ['name' => 'frequency_type', 'contents' => 'yearly'], ['name' => 'frequency_count', 'contents' => '5'], ['name' => 'metadata[location]', 'contents' => 'Mountain Resort'], ['name' => 'metadata[expected_attendees]', 'contents' => '150'], [ 'name' => 'attachments[]', 'contents' => fopen('path/to/schedule.pdf', 'r'), 'filename' => 'retreat_schedule.pdf', ], [ 'name' => 'images[]', 'contents' => fopen('path/to/venue.jpg', 'r'), 'filename' => 'retreat_venue.jpg', ], ['name' => 'notes[0][content]', 'contents' => 'Remember to book flight tickets for overseas participants.'], [ 'name' => 'notes[0][attachments][]', 'contents' => fopen('path/to/flight_details.pdf', 'r'), 'filename' => 'flight_details.pdf', ], ]; $response = $client->post('api/events', [ 'multipart' => $multipart, ]); $eventData = json_decode($response->getBody(), true); echo "Event created with ID: " . $eventData['id']; ``` ### Get Event Details [](#get-event-details) ``` $eventId = 1; $response = $client->get("api/events/{$eventId}"); $event = json_decode($response->getBody(), true); ``` ### Update an Event [](#update-an-event) ``` $eventId = 1; $response = $client->put("api/events/{$eventId}", [ 'json' => [ 'name' => 'Updated Event Name', 'description' => 'This is an updated description', 'start_date' => '2024-08-01 10:00:00', ], ]); $updatedEvent = json_decode($response->getBody(), true); ``` ### Delete an Event [](#delete-an-event) ``` $eventId = 1; $response = $client->delete("api/events/{$eventId}"); echo $response->getStatusCode() == 204 ? "Event deleted successfully" : "Failed to delete event"; ``` ### Get Past Events [](#get-past-events) ``` $response = $client->get('api/events/past'); $pastEvents = json_decode($response->getBody(), true); ``` ### Get Future Events [](#get-future-events) ``` $response = $client->get('api/events/future'); $futureEvents = json_decode($response->getBody(), true); ``` ### Get Events by Status [](#get-events-by-status) ``` $status = 'active'; $response = $client->get("api/events/status/{$status}"); $activeEvents = json_decode($response->getBody(), true); ``` Notes ----- [](#notes-1) ### Add a Note to an Event [](#add-a-note-to-an-event) ``` $eventId = 1; $response = $client->post("api/events/{$eventId}/notes", [ 'json' => [ 'content' => 'This is a new note for the event', ], ]); $note = json_decode($response->getBody(), true); ``` ### Update a Note [](#update-a-note) ``` $eventId = 1; $noteId = 1; $response = $client->put("api/events/{$eventId}/notes/{$noteId}", [ 'json' => [ 'content' => 'This is an updated note content', ], ]); $updatedNote = json_decode($response->getBody(), true); ``` ### Delete a Note [](#delete-a-note) ``` $eventId = 1; $noteId = 1; $response = $client->delete("api/events/{$eventId}/notes/{$noteId}"); echo $response->getStatusCode() == 204 ? "Note deleted successfully" : "Failed to delete note"; ``` Attachments ----------- [](#attachments) ### Add an Attachment to an Event [](#add-an-attachment-to-an-event) ``` $eventId = 1; $response = $client->post("api/events/{$eventId}/attachments", [ 'multipart' => [ [ 'name' => 'attachment', 'contents' => fopen('path/to/document.pdf', 'r'), 'filename' => 'important_document.pdf', ], ], ]); $attachment = json_decode($response->getBody(), true); ``` ### Remove an Attachment from an Event [](#remove-an-attachment-from-an-event) ``` $eventId = 1; $attachmentId = 1; $response = $client->delete("api/events/{$eventId}/attachments/{$attachmentId}"); echo $response->getStatusCode() == 204 ? "Attachment removed successfully" : "Failed to remove attachment"; ``` Images ------ [](#images) ### Add an Image to an Event [](#add-an-image-to-an-event) ``` $eventId = 1; $response = $client->post("api/events/{$eventId}/images", [ 'multipart' => [ [ 'name' => 'image', 'contents' => fopen('path/to/image.jpg', 'r'), 'filename' => 'event_image.jpg', ], ], ]); $image = json_decode($response->getBody(), true); ``` ### Remove an Image from an Event [](#remove-an-image-from-an-event) ``` $eventId = 1; $imageId = 1; $response = $client->delete("api/events/{$eventId}/images/{$imageId}"); echo $response->getStatusCode() == 204 ? "Image removed successfully" : "Failed to remove image"; ``` These examples cover all the main operations available through the Event User Manager API. Remember to replace `'http://your-api-base-url/'` with your actual API URL and `'YOUR_API_TOKEN'` with a valid authentication token. Also, adjust file paths in the examples to match your local file structure. This example demonstrates creating an event with: - Basic event details (name, description, dates, status) - Event type and recurrence pattern - Metadata (location and expected attendees) - Main event attachments and images - Notes with their own attachments and images Remember to replace `'http://your-api-base-url/'` with your actual API URL and `'YOUR_API_TOKEN'` with a valid authentication token. ### Filament Admin [](#filament-admin) The package includes Filament resources for managing events, event types, and recurrence patterns. These will be automatically available in your Filament panel. ### Notifications [](#notifications) The package includes a configurable notification system. You can add custom notification channels by editing the configuration file. Customization ------------- [](#customization) You can extend or override any functionality of the package. Refer to the configuration file for customization options. Testing ------- [](#testing) ``` composer test ``` Changelog --------- [](#changelog) Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently. Contributing ------------ [](#contributing) Contributions are welcome! Please see [CONTRIBUTING](.github/CONTRIBUTING.md) for details. Security -------- [](#security) If you discover any security-related issues, please email instead of using the issue tracker. Credits ------- [](#credits) - [Kellvem Barbosa](https://github.com/kellvembarbosa) - [All Contributors](../../contributors) License ------- [](#license) The Event User Manager is open-sourced software licensed under the [MIT license](LICENSE.md). ### Health Score 27 — LowBetter than 49% of packages Maintenance37 Infrequent updates — may be unmaintained Popularity6 Limited adoption so far Community7 Small or concentrated contributor base Maturity49 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure 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 ~0 days Total 2 Last Release 601d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/ea0811b77232bb232cc41a918466de4b146044ce293582045f2df13eeeeffd7f?d=identicon)[bambolee-digital](/maintainers/bambolee-digital) --- Top Contributors [![kellvembarbosa](https://avatars.githubusercontent.com/u/3621135?v=4)](https://github.com/kellvembarbosa "kellvembarbosa (9 commits)") ### Embed Badge ![Health badge](/badges/bambolee-digital-event-user-manager/health.svg) ``` [![Health](https://phpackages.com/badges/bambolee-digital-event-user-manager/health.svg)](https://phpackages.com/packages/bambolee-digital-event-user-manager) ``` ### Alternatives [lab404/laravel-impersonate Laravel Impersonate is a plugin that allows to you to authenticate as your users. 2.3k16.4M48](/packages/lab404-laravel-impersonate)[santigarcor/laratrust This package provides a flexible way to add Role-based Permissions to Laravel 2.3k5.4M42](/packages/santigarcor-laratrust)[overtrue/laravel-follow User follow unfollow system for Laravel. 1.2k404.7k5](/packages/overtrue-laravel-follow)[althinect/filament-spatie-roles-permissions 340954.7k9](/packages/althinect-filament-spatie-roles-permissions)[stephenjude/filament-two-factor-authentication Filament Two Factor Authentication: Google 2FA + Passkey Authentication 81158.7k4](/packages/stephenjude-filament-two-factor-authentication)[marcelweidum/filament-passkeys Use passkeys in your filamentphp app 5925.8k](/packages/marcelweidum-filament-passkeys) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)