Libraries tagged by laramote

Keeps track of the original UTM parameters

Go to Download

A packages to help create filters to queries based on request parameters

Go to Download

The purpose of this class is to clear all the input parameters in an HTTP request by avoiding the passage of SQL Injection made by bad intentioned people.

Go to Download

It offers a convenient way to create a user operation log for any Laravel 5 application. Supports parameters and writes log to database by default but can also be linked to different repositories.

Go to Download

PHP class for serving parameters

Go to Download

Addon for Symfony bundle for transform parameters of request to DTO. Bitrix specify part

Go to Download

Symfony bundle for transform parameters of request to DTO.

Go to Download

Convert dotted form parameters to array format / ドット区切りのフォームパラメータを配列形式に変換してRequestに設定します。

Go to Download

Composer plugin to create locally specific configuration from set of template files and from file with configuration parameters.

Go to Download

Generates a not unique integer hash from an integer. You can set a optional max size parameter.

Go to Download

Helps to build parameters.yml file based on environment variables

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.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

Calculation of trend line parameters for a given set of chart points

Go to Download

This library is a Singleton (anti)pattern implementation using a Traits with a support for an Object Inheritance and passing parameters to the constructor.

Go to Download

Generate a URL with unique parameters and a signature to prevent invalid accesses.

Go to Download