Libraries tagged by model saver
mohit-yogi/async-db-helper
1 Downloads
Save the model data to redis & then move them to DB later
mgahed/ai
2 Downloads
This is my AI package that collecting several AI models from different providers
joeri-abbo/starship
2 Downloads
A package to craft several different models for wordpress
fad/yii-synctranslit
278 Downloads
Translit text via javascript or save transliterated model attribute text via behavior
nolazybits/propel2-geocodable-behavior
1818 Downloads
The GeocodableBehavior helps you build geo-aware applications. It automatically geocodes your models when they are saved, giving you the ability to search by location and calculate distances between records.
hmic/cakephp-blame
186 Downloads
CakePHP plugin for blaming a user (from AuthComponent) for save action on models.
emidia/yii2-jsonify
538 Downloads
Behavior that convert array to JSON before save data in model
miladev/lara-meta
6 Downloads
Save meta with any model.
code-corner/opencart-shell
5 Downloads
use to create extension and controller, language, model, template, library it will save your max time to create files.
code-corner/cscart-shell
1 Downloads
use to create extension and controller, language, model, template, library it will save your max time to create files.
abdelhafz/trans-accessor
4 Downloads
simple model translate accessor that help save yor time and make you dry
t3/extbase-session-entities
989 Downloads
Extends TYPO3's Extbase framework by possibility to work with session entities over several actions without persisting, including partial model validation.
mvnrsa/laravel-sluggable-trait
12 Downloads
A trait you can apply to Eloquent models to have slugs automatically generated on save. A slight omprovement on martinbean/laravel-sluggable-trait to use underscore (or any other character) instead of dash in slugs.
gurzhii/laravel-sluggable-trait
267 Downloads
A trait you can apply to Eloquent models to have slugs automatically generated on save.
tslol/docker-api-php
2 Downloads
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..." } ```