Libraries tagged by insite

Communicate with a DynamoDB instance from inside your symfony 2 application.

Go to Download

Communicate with your AWS infrastructure from inside your Symfony 2 application

Go to Download

Display plain images in a nice slideshow (using a Lightbox or not). Select the images directly or choose a directory to show all images inside that directory.

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

The special function "elo" that can be used instead of the standard "var_dump" method with the "Yakalelo" phrase.

Go to Download

Run Laravel (or Lumen) tasks and queue listeners inside of AWS Elastic Beanstalk workers

Go to Download

This package mainly combine all the files inside lang folder and give the wrapper which will either collect information from the combined file or as a fallback if particular key is not defined collect from original file through a helper

Go to Download

Use Filters instead of Requests in your Laravel projects to be more versatile.

Go to Download

Project template for Resilient distributions inside DrupalVM.

Go to Download

inside project

Go to Download

A small pagination library that produces data objects instead of HTML.

Go to Download

Finds individual items inside an image and gets their size/coordinates.

Go to Download

Organize resource pages in sidebar instead of putting all the buttons and links elsewhere in order to make navigation between pages more comfortable.

Go to Download

Access the NS PHPToolkit API inside your Symfony application

Go to Download

Implementation Rubaxa/Sortable for Yii2. Sortable grid view inside.

Go to Download