Libraries tagged by Ensue

Analyze objects relation. Ensure that objects can be deleted using introspection.

Go to Download

The Laravel Invoice Number Generator is a powerful and flexible package that simplifies the process of generating unique invoice numbers within Laravel applications. It provides a convenient solution for managing invoice numbers, ensuring they are unique, sequential, and customizable according to your specific requirements.

Go to Download

This package provides a validator for ensuring strong passwords in Laravel 4 applications.

Go to Download

This package provides a validator for ensuring strong passwords in Laravel 4 applications.

Go to Download

Empower your platform to seamlessly accept Whapple Pay payments with the Whapple Pay SDK. This comprehensive software development kit offers developers a robust solution for integrating Whapple Pay payment capabilities into their applications, ensuring a smooth and secure payment experience for users. Simplify payment processing and enhance user convenience with the Whapple Pay SDK, designed to streamline payment workflows and deliver exceptional payment acceptance functionalities.

Go to Download

Manage your QR code campaigns all in one place. Create branded QR codes and handle redirects intelligently to ensure proper attribution for your campaign sources.

Go to Download

Ensure that the LastEdited field is indexed so that performance for partials is consistent with large sites

Go to Download

Eloquent Event Logger is a logging tool for Laravel's Eloquent ORM. It's designed to automatically record and log events for Laravel Eloquent model's operations such as creation, updates and deletions. Detailed event logs help facilitate debugging and keep track of changes made to models over time. It's a tool for monitoring your application's data layer, ensuring data integrity, and aiding in development.

Go to Download

Composer helps you declare, manage and install dependencies of PHP projects, ensuring you have the right stack everywhere.

Go to Download

Array class that ensures it ne'er has duplicate values.

Go to Download

Validates strings like "(()()()()))((((()()()))(()()()(((()))))))" to ensure counts of opening and closing brackets are equal.

Go to Download

Designed to ensure security on web authentication systems.

Go to Download

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.44) is used. For example, calling `/info` is the same as calling `/v1.44/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 [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (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

Provides a SCSS compiler compatible with wp_enqueue_style() for rapid CSS development in themes and plugins.

Go to Download

A distribute image storing and availability ensuring system.

Go to Download