Libraries tagged by operating

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

Perform transactional operations with MongoDB

Go to Download

Helper classes for Currency Exchange operations

Go to Download

A library to easily handle date operations

Go to Download

Safety operations with numbers.

Go to Download

Advance PHP math calculator with complex operations.

Go to Download

A thin wrapper around PDO for common MySQL operations.

Go to Download

Collection of database classes to allow database operations and unit testing

Go to Download

Helper for system operation.

Go to Download

Rule-based generation of fixture databases by sampling operational databases

Go to Download

Most commanly used buttons in Laravel for CRUD operations

Go to Download

editable and historiable data for crud operations to save request consumptions and bandwidth, also for make history for all changes done in the request.

Go to Download

Arithmetic Operation

Go to Download

Magento module responsible for catalog gallery processor delete operation handling

Go to Download

Delete Orders by MageINIC, The Magento 2 Delete Orders extension empowers administrators to efficiently remove unwanted orders, invoices, shipments, and credit memos from the backend, ensuring a streamlined and organized e-commerce operation. Simplify order management, maintain data consistency, and enjoy the flexibility to enable or disable deletion features as needed.

Go to Download