Libraries tagged by model support

Supports multi-processing event-driven model

Go to Download

Extension to the Laravel Schema Builder to support audit-tracking fields in models.

Go to Download

Component add support translatable properties to ActiveRecord models

Go to Download

Laravel helper package to create CRUD controllers, views, models, jobs with 1 command. Vue.js support.

Go to Download

Multi Auth in Laravel Project with support for the Laravel 8 Models namespace convention & optional generation inside a tenant when using the multitenancy stancl/tenancy package. Forked from bitfumes/laravel-multiauth

Go to Download

Provides UUID Support for Laravel 4 Eloquent Models

Go to Download

A trait that provides support for uuid for eloquent models.

Go to Download

This package is a Laravel extension for easy translation of model attributes, enabling seamless multi-language support in your application.

Go to Download

PHPExcel wrapper for Yii Framework with support for data providers and models

Go to Download

Adds sortable behavior and ordering to Laravel Eloquent models. Grouping and many to many supported.

Go to Download

A Laravel package providing a fuzzy search trait for Eloquent models to easily implement search functionality with support for concatenated attributes.

Go to Download

Adds support for UUID generation automatically for Models Eloquents.

Go to Download

A simple trait to add support for aggregate functions in Eloquent models

Go to Download

Provides support for ActiveRecord variation via related models in Yii2

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