Libraries tagged by model meta

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

Will aid in the caching of expensive helper/model instance methods.

Go to Download

The TatTran Repository is a Laravel package designed to supercharge your app's speed by caching database queries and model operations. This means your app can retrieve data instantly, leading to a smoother user experience.

Go to Download

PHPStan rules that make sure your models are only being mutated from within its Domain.

Go to Download

Adds a $model->saveWithAuditTrail() method to your Models allowing you to annotate changes to your data.

Go to Download

Laravel tool to log model-specific messages and metrics

Go to Download

Provides common base classes used for some of Coyote6 GraphX's developed projects. Provides UUID trait for models using it as a primary key. Provides trait methods to return models as options.

Go to Download

A trait that adds a method to a WordPress model for the post title.

Go to Download

A trait that adds a method to a WordPress model for the post ID.

Go to Download

A trait that adds a method to a WordPress model for the post excerpt.

Go to Download

A trait that adds a method to a WordPress model for the post content.

Go to Download

A quick and easy way to build prototype GraphQL queries and mutations for your Laravel models and controllers.

Go to Download

Expose your eloquent models as GraphQL queries and mutations

Go to Download

A handy method for accessing a model's value as an API resource

Go to Download

A Larave package to show accessor, mutator and scope of a specific model.

Go to Download