Libraries tagged by running

PHP SDK for interacting with the Ollama API, a service for running and deploying large language models.

Go to Download

Fixed the Sublime editor link path when running a project from a VM

Go to Download

Docker files for running a basic Symfony application.

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

Installation for deploying or running laravel project by server requirements

Go to Download

Allow MODX to have composer managed packages running Blend Migrations and using lci/console for cli commands.

Go to Download

A simple PHP wrapper for running JavaScript code

Go to Download

This plugin allows to interact with Metasploit framework either through msfrpcd deamon or the msgrpc plugin running in msfconsole.

Go to Download

Yii2 background task queue Extension is a simple and easy-to-use extension for running background tasks in Yii2 applications

Go to Download

Running php built-in web server via altax.

Go to Download

With a single Artisan command, in a fresh Laravel application, you get up and running with a fully functional Single Page Application (SPA) using Vue and Vue Router ready for you to build something wonderful.

Go to Download

Process Manager helps you to see statuses for long running Processes

Go to Download

An independent client for Kibilog.com, running on native code.

Go to Download

Component for running Docker images in KBC

Go to Download

A platform-independent way to retrieve the list of processes running on your systems. It works both on the Windows and Unix platforms.

Go to Download