Libraries tagged by operating

Use the Taxonomy API to discover the most appropriate eBay categories under which sellers can offer inventory items for sale, and the most likely categories under which buyers can browse or search for items to purchase. In addition, the Taxonomy API provides metadata about the required and recommended category aspects to include in listings, and also has two operations to retrieve parts compatibility information.

Go to Download

Perform vector operations natively on MySQL using openAI embeddings

Go to Download

CakePHP Front operations plugin

Go to Download

A static, simple PDO wrapper for easy database operations

Go to Download

Basic CRUD operations in the Yii2 framework

Go to Download

This library helps you write your own HTML code and manage operations in your back-end

Go to Download

This is the use of magento2 scheduled tasks perform their own shell command to back up the database operation.

Go to Download

The Laravel Logger project is a robust logging solution tailored for Laravel applications, designed to provide comprehensive monitoring, tracking, and analysis of system activities and events. Developed with the Laravel framework, this logging system offers seamless integration, ensuring smooth operation within Laravel-based projects.

Go to Download

Bitmask class helps you to use all might of bit masks and don't care about what bitwise operations are. It represents a high-level abstraction that looks like simple and manageable object and behaves like collection.

Go to Download

Quik is designed to shorthand typical Magento operations so that you don't have to remember everything.

Go to Download

A small library for attempting operations with graceful retries, based on an idea by igorw/retry

Go to Download

helper classes for datetime operations

Go to Download

A genereic intreface for operatives and conectives

Go to Download

The extension allows to check connection to db, mail operation and secrets.json for compliance

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