Libraries tagged by naemon

A Laravel Doctrine friendly daemonising queue worker for Laravel 5

Go to Download

Simple daemon in PHP for running background job on server. Uses MongoDB as MessageQueue for job descriptions.

Go to Download

A coin daemon implementation in PHP. It is compatible with most coins through configuration.

Go to Download

Interact with the Systemd Notify daemon for service lifecycle integration. A PHP 8 fork of aethalides/systemd-notify

Go to Download

Batch process Laravel Queue without a daemon; Processes queue jobs and kills the process

Go to Download

Simple picture and video file sorting service/daemon for linux written in PHP. It takes photos & videos from a source directory and sorts the photos into Y/M folders and the videos into Y folders (ie. dest_path/2014/January).

Go to Download

Long-living MySQL connection for daemon.

Go to Download

PHP daemon for managing gearman workers

Go to Download

PHP daemon for managing gearman workers

Go to Download

supervisor for daemon, service, etc...

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

PHP daemon library

Go to Download

PHP Wrapper for a bitcoind daemon

Go to Download

A PHP daemon factory for handling websocket communication based on ReactPHP and Ratchet.

Go to Download

A php daemon that runs shell commands channeled through a websocket. Based on ReactPHP and Ratchet.

Go to Download