Libraries tagged by s.id
undf/angular-utrans
101 Downloads
Symfony2 and AngularJS module for client side translations
ugo/datatable
2 Downloads
Server side datatable calls
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..." } ```
trackfinity/trackfinity-php-client
6 Downloads
Client side library for rule based traffic filtering on a web site.
totop275/ss-datatables
39 Downloads
A handler for datatables server side's request
tollwerk/tw-squeezr
15 Downloads
TYPO3 extension version of squeezr, another take on device-aware adaptive images and server side CSS3 media queries
tohir/formgenerator
167 Downloads
PHP Form Generator with both Client-Side (jQuery Validation Plugin) and Server-Side Validation
tkriek/copernica-api-php
844 Downloads
Bindings and implementation of the REST side of the Copernica API
themexpert/react-filemanager-server
81 Downloads
Server side library for React File Manager
themeplate/blocks
25 Downloads
ThemePlate server side rendered block
tetsuo13/matomo_tracking_api
35 Downloads
Add Matomo tracking server-side code to all requests in Roundcube
tencentcloudbase/tcb-manager-php
458 Downloads
tencentcloudbase management side sdk for php
techliance/marvel
98 Downloads
This package will help you build crud for api and admin side, with js frameworks like AngularJS and VueJS.
teameh/silex-react-renderer-provider
32 Downloads
Client and Server-side react rendering as a Silex service provider
taufik-nurrohman/minify
1 Downloads
Reduce CSS, HTML, JavaScript, JSON, PHP, and XML code size on the server side.