Libraries tagged by deepr

Faker provider for fantasy names. Support for the deprecated faker and standalone

Go to Download

Librería en PHP para la prueba BECK:BDI Síntomas de depresión

Go to Download

This is a fork of an older verions of PHP HTTP client - https://github.com/guzzle/guzzle3. This library is deprecated in favor of https://packagist.org/packages/guzzlehttp/guzzle

Go to Download

A cache interface to store files (deprecated)

Go to Download

Inherit any setting from any model infinitely deep

Go to Download

A Laravel package for deep cloning Eloquent models and their nested relationships.

Go to Download

[DEPRECATED] A Pusher bridge for Laravel

Go to Download

PHP implementation of Deep Thought

Go to Download

A composable, JSONPath-inspired query engine for deep property access in PHP

Go to Download

A chainable, lightweight library for maniplating(i.e. query/update/delete...) deep nested array

Go to Download

Create deep copies (clones) of your objects

Go to Download

Create deep copies (clones) of your objects

Go to Download

Create dynamic deeplink for android and iOS apps.

Go to Download

Generic function and convention to trigger deprecation notices

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