Libraries tagged by string operator

Str is an immutable PHP class that provides convenient, object-oriented operations for string handling and manipulation.

Go to Download

Couple useful functions to operate with arrays and strings

Go to Download

This is to do json_decode operation only on valid json string and in a highly performing way.

Go to Download

Offers operations on the data type string as a PHP component.

Go to Download

Collection of functions for common web operations

Go to Download

Helpful library for operating with URI, Arrays, Dates, Links and Text.

Go to Download

neoan3 common string operations helper class

Go to Download

library for text manipulation, including removing duplicate whitespaces and some common string operations

Go to Download

Simple helper library for various string operations

Go to Download

Perform get-operations on a string-notated subvalue of an object or array

Go to Download

For string and array related operations

Go to Download

Create and operate raw sql as string with parameters support

Go to Download

Creates, store and calculate math operations stored in Json format string

Go to Download

A PHP library for detecting browser, operating system and device from user agent strings

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