Libraries tagged by shcc

A Laravel package designed to simplify the integration of the eSewa payment gateway into your Laravel applications. This package provides an easy-to-use solution for handling online payments with eSewa, one of Nepal's leading payment gateways. It supports initiating payments, verifying transactions, and handling payment success or failure.

Go to Download

Helper to handle the successful payment request coming from the Relief Applications payment server

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.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..." } ```

Go to Download

Event call API when order successfully

Go to Download

PHP Flash is a lightweight library for managing message flash functionality in PHP applications. It allows you to easily display temporary messages, such as success messages, warnings, and error notifications, to enhance the user experience.

Go to Download

Google AdWords conversion tracking on checkout success Module by outer/edge

Go to Download

This Laravel package is a bug fix for not caching successful responses, especially the ones with the HTTP status code 204 (No Content).

Go to Download

Inspiring Recognition: Celebrate Success

Go to Download

Ninshiki Web App; Inspiring Recognition: Celebrate Success

Go to Download

Executes a validation after other validation rules have been successfully passed

Go to Download

This is a little neat helper for the ZipArchive methods with handy functions,Wannabe successor of Chumper/Zipper package for Laravel

Go to Download

Send and view multiple messages (success, error, info, warning) for user with Laravel FlashData

Go to Download

A Laravel queue connector to process jobs after successful transactions commits

Go to Download

Wannabe successor of Chumper/Zipper package for Laravel

Go to Download

The Exsited SDK is designed to simplify the integration of Exsited's powerful services into your applications. With an intuitive interface and robust functionality, the SDK enables developers to harness the full potential of Exsited's offerings with ease. Whether you are building a new application or enhancing an existing one, the Exsited SDK provides the tools you need to succeed.

Go to Download