Libraries tagged by event system

mrnewport/laravel-flow

3 Favers
0 Downloads

Production-ready, domain-agnostic flow system for Laravel with multi-step, assignment, events, and notifications.

Go to Download


kama812/laravel-comments

1 Favers
27 Downloads

Comments system for your Laravel application. Features: can be used to comment on any model, HTML filter customization (HTMLPurifier), API, comment rating, replies, events, auth rules ...

Go to Download


jds/trevron

0 Favers
4 Downloads

Basic Framework with Authorization, Events, Migrations, Middleware, CSRF Tokens and JWT tokens. Only to be used by JDS (Jessop Digital Systems) or for Educational Purposes. Not for Production Use!

Go to Download


dipesh/calendar

3 Favers
46 Downloads

A PHP package that builds a complete Nepali calendar effortlessly, serving as a wrapper around the dipesh/nepali-date package. It allows users to generate and manipulate a full Nepali calendar, add events, and perform date calculations without any prior knowledge of the underlying system.

Go to Download


devium/processes

24 Favers
17976 Downloads

This package is used to get a list of running processes on Windows or Unix-like systems, even Darwin

Go to Download


smmoosavi/php-gettext

19 Favers
23665 Downloads

Wrapper for php-gettext by danilo segan. This library provides PHP functions to read MO files even when gettext is not compiled in or when appropriate locale is not present on the system.

Go to Download


lucatacconi/crunz-ui

15 Favers
1387 Downloads

User interface for lavary/crunz. Integrate Crunz library and funtions: Tabular, monthly or weekly interface to view the scheduled and executed tasks. Quick display of the execution result of the tasks that have been executed (Indicator icons easily show the result). Upload, download, edit or delete tasks. Forced run of the task, even outside the scheduled time with eventual display of the log once the execution is completed. It can be used with integrated Crunz or with a version of Crunz already installed on the system

Go to Download


smmoosavi/php-gettext-core

2 Favers
22898 Downloads

php-gettext by danilo segan. This library provides PHP functions to read MO files even when gettext is not compiled in or when appropriate locale is not present on the system.

Go to Download


jf/event

0 Favers
445 Downloads

Sistema de eventos PSR-14

Go to Download


foolz/theme

5 Favers
1715 Downloads

An opinionated theme system where even the views can be classes, and everything is a plugin.

Go to Download


hongyukeji/plugin-theme

0 Favers
5 Downloads

An opinionated theme system where even the views can be classes, and everything is a plugin.

Go to Download


cullylarson/wp-deploy-database-sync

0 Favers
49 Downloads

A library for syncing Wordpress databases. Supports syncs to and from local and remote machines, and even remote to remote syncs. Also supports search and replace. Useful as part of a deployment system.

Go to Download


behzaddev/searchable

0 Favers
0 Downloads

Search Package OverviewThe Search package is a powerful tool designed to facilitate efficient and effective search operations within various datasets or databases. It provides a set of functions and classes that enable users to perform complex search queries, filter results, and retrieve relevant data with ease. The package is highly customizable, allowing users to define their own search criteria, implement sorting mechanisms, and handle large volumes of data seamlessly.Key Features: Customizable Search Queries: Users can create tailored search queries using various operators and conditions, making it possible to perform both simple and advanced searches. Sorting and Filtering: The package includes built-in methods to sort and filter search results, enabling users to organize data based on specific parameters such as date, relevance, or custom fields. Scalability: Designed to handle large datasets, the Search package is optimized for performance, ensuring quick response times even with millions of records. Integration: The package is compatible with a variety of databases and data sources, making it a versatile solution for different types of projects. User-Friendly Interface: It offers a straightforward API that is easy to use, even for those who are not experts in programming. This allows a broader audience to leverage the power of advanced search capabilities.Use Cases: Data Analysis: Quickly find and retrieve specific information from large datasets for analysis. Content Management Systems: Implement efficient search functionality in content-heavy websites or applications. E-commerce: Enhance product search features in online stores, improving the user experience by providing relevant results swiftly. Knowledge Bases: Help users find relevant articles or documentation based on keyword searches.Overall, the Search package is an essential tool for anyone needing to implement or enhance search functionality in their applications, providing both power and flexibility in managing and retrieving data.

Go to Download


piurafunk/docker-php

0 Favers
9 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


maxvaer/docker-openapi-php-client

0 Favers
4 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


<< Previous Next >>