Libraries tagged by supportbee

Yii2 Queue Extension which supported DB, Redis, RabbitMQ, Beanstalk, SQS and Gearman

Go to Download

Yii2 Queue Extension which supported DB, Redis, RabbitMQ, Beanstalk, SQS and Gearman

Go to Download

Persistent settings manager for laravel, translations are supported.

Go to Download

A Magium module for validating MailChimp integration. Note - this is a community project; it is not supported by Mailchimp

Go to Download

This Hvya supported module provides Quick shop button on products and add to cart ajax feature as well.

Go to Download

Simple muti-sms gateway package for sending short text messages from your Application.Facade for Laravel 5.Currently supported Gateways Alidayu, Webpower /Any HTTP/s based Gateways are supported by Custom Gateway. Log gateway can be used for testing.

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 Laravel 5 Package for Indian Payment Gateways. Currently supported gateways: CCAvenue, PayUMoney, EBS, CitrusPay, InstaMojo

Go to Download

Magento 2 Flash Sales Graph QL supported.

Go to Download

CakePHP plugin for creating and/or rendering Pdfs, several Pdf engines supported.

Go to Download

PHP math captcha. Laravel supported

Go to Download

An SDK allowing easy conversion from any supported format to PDF using the PDFen.com API

Go to Download

Persistent settings manager for laravel, translations are supported.

Go to Download

Yii2 Queue Extension which supported DB, Redis, RabbitMQ, Beanstalk and Gearman

Go to Download

Handle session save data, supported save to file, database, MemCache, Redis

Go to Download