Libraries tagged by running.fm

Yii2 component for running operations in the background.

Go to Download

A Laravel 4 helper command for organizing and running phpunit testsuites

Go to Download

Docker files for running a basic Laravel application.

Go to Download

An implementation of GenericProvider for XenForo boards running bdApi

Go to Download

Assists with running Moodle plugins in Travis CI. Based on Moodlerooms initial work

Go to Download

PHP tools to build robust long-running processes

Go to Download

A CLI job queue for running multiple commands in parallel

Go to Download

Get up and running with subscriptions in your Laravel app in minutes instead of days

Go to Download

This package for creating and running fillers on laravel projects

Go to Download

Docker files for running a basic QuantaForge application.

Go to Download

Profile running queues with various libraries and SaaS products.

Go to Download

Firestore wrapper for Laravel app running inside Google App Engine.

Go to Download

Running a job board inside Contao has never been easier.

Go to Download

Official PHP integration for the Pixaven Image API - enterprise-grade image processing SaaS running entirely on Apple® platform. Resize, scale, crop, mask, filter and enhance your images with blazing speed.

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