Libraries tagged by deprem

✗ [DEPRECATED] Jigoshop driver for the WordPress payment processing library.

Go to Download

✗ [DEPRECATED] iThemes Exchange driver for the WordPress payment processing library.

Go to Download

✗ [DEPRECATED] ClassiPress driver for the WordPress payment processing library.

Go to Download

✗ [DEPRECATED] AppThemes driver for the WordPress payment processing library.

Go to Download

Service Locator Generator

Go to Download

Depreceated

Go to Download

Interfaces for generic extractor modules (deprecated)

Go to Download

DDump Bundle to dump and optionnaly exit

Go to Download

Go to Download

Fix for DOMNodeInserted deprecated issue in Bolt 5

Go to Download

DEPRECATED: JavaScript client for the Wikibase Repository web API

Go to Download

Adds option to add an image setting field with Voce_Settings_API. Deprecated Plugin - Please use https://github.com/voceconnect/voce-media-setting as a replacement for >= WP 3.5 compatibility

Go to Download

Simple wrapper for Git, based on deprecated sebastianbergmann/git

Go to Download

A sample module that show what and how to use instead of deprecated Registry class since Magento 2.3

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