Libraries tagged by remoteid

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.41) is used. For example, calling `/info` is the same as calling `/v1.41/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

Logging using Gelf for storage on a remote server. Registration of Requisition Logs and Laravel Logs.

Go to Download

A little PHP script which is a demonstration usage for Plinker - Remote coded tasks run as root!

Go to Download

Project json for Acquia Remote Administration Composer builds via Jenkins build server

Go to Download

Adds Drush command(s) to scaffold out HTTP client(s) for interacting with remote APIs in Drupal modules.

Go to Download

PHP SDK Recast.AI with Explicit Require Autoload Statements Removed

Go to Download

HTTP middleware to get code coverage of Laravel applications on remote servers

Go to Download

Extensible PHP library to export domain data into a formatted document stored in a remote storage for backup purposes.

Go to Download

Extensible PHP library to export domain data into a formatted document stored in a remote storage for backup purposes. This library contains the shared model that must be provided by a downstream project.

Go to Download

A PHP class to backup, disable, destroy, or completely erase PHP applications remotely in special cases.

Go to Download

PHp Robot Remote Server

Go to Download

Library for generating QR codes both locally and remotely.

Go to Download

PHP Wrapper for MaxCDN Remote Web Services

Go to Download

git remote add origin [email protected]:jenn0pal/airspeedapi-php.git

Go to Download

Remote server error bundle

Go to Download