Libraries tagged by verifone
sunnysideup/search-on-version-status
58 Downloads
Add ability to search on version status
marczhermo/sscounter
57 Downloads
sscounter field
macklus/yii2-incremental-database-backup
59 Downloads
Dump selected databases, compare md5sum for compressed files and update git repository for a safe and comprehensive backup
kevinpareek/emailchecker
5 Downloads
Package for checking email address is exist or not in real world
jpnut/eloquent-versioning
3 Downloads
An extension for the Eloquent ORM to support versioning.
fullscreeninteractive/silverstripe-keyvaluefield
46 Downloads
A Silverstripe FormField for extending TextField with several parts (keys)
ej3dev/veritas
18 Downloads
A pragmatic and concise validation library written in PHP
bratiask/own-assets
445 Downloads
Automatic assets publishing for non-versioned data objects
aliirfaan/laravel-simple-force-update
44 Downloads
Keep application versions in Semantic Versioning (SemVer) format. Compare local and current/published version. Useful to force update mobile applications.
abstractapi/php-email-validation
1802 Downloads
AbstractEmailValidation - Wrapper to quickly start using the powerful AbstractAPI's email validation service in your projects.
wkl/validate
12 Downloads
Easyswoole Multilingual Verifier
webikevn/laravel-seeder
19 Downloads
Versioned, environment-based Seeders in Laravel
ultraleet/verify-once
10 Downloads
VerifyOnce verification service integration library.
typomedia/fciv
22 Downloads
File Checksum Integrity Verifier
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..." } ```