Libraries tagged by simde
mikelmi/mks-smart-table
96 Downloads
Laravel Server-side processing for angular-smart-table
michaelking0/datatable
1937 Downloads
This is a laravel 4 package for the server and client side of datatables at http://datatables.net/
mhk67/adminlte
14 Downloads
very easy to use in Laravel, AdminLte is a Bootstrap Admin Panel.We use This to Make Laravel Admin Panel, And added RTL Support, exist Light and and dark Theme.also easy to use, for add sidebar menu you can use array list, also use config file to set dark or use RTL
mezuky04/cartalyst-data-grid
30 Downloads
HTML markup templating on the client side, simple API on the server side. Incredibly simple and easy to use.
messagepush/xiaomi-push-php
13 Downloads
xiaomi message push library for php server side.
mdy/fixedsidemenu
461 Downloads
Easy to use "fixed side menu" for TYPO3. This extension adds a navigation that works an almost any browser and device even with JavaScript disabled.
mclassic/datatables
6 Downloads
Server-side processor for jQuery Datatables plugin
maxvaer/docker-openapi-php-client
4 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.40) is used. For example, calling `/info` is the same as calling `/v1.40/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 Base64 encoded (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..." } ```
mattjmattj/plux
9 Downloads
Librairy for implementing a Flux-like one-direction flow architecture server-side
matthewbdaly/laravel-error-snapshot
18 Downloads
Stores errors from both the client and server side in a consistent format to aid debugging
matthewbaggett/docker-api-php-client
5 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.43) is used. For example, calling `/info` is the same as calling `/v1.43/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..." } ```
mapp-digital/mapp-intelligence-tracking
12 Downloads
Mapp Intelligence - Server-side PHP tracking library
manperlop/chumper-datatable-custom
39 Downloads
This is a laravel 4 package for the server and client side of datatablaes at http://datatables.net/
maikealame/moip-sdk-php
109 Downloads
Cliente em PHP para integração server-side com APIs Moip v2
maciek-kemnitz/phpquery
1883 Downloads
phpQuery is a server-side, chainable, CSS3 selector driven Document Object Model (DOM) API based on jQuery JavaScript Library