Libraries tagged by remoteid

A lite version of yajra/laravel-datatables, with HTML builders & exporting removed.

Go to Download

Remote Procedure Call Library

Go to Download

Magento 2 utility module for migrating/managing cms pages and block data from local environment to remote

Go to Download

A cron component which allows you to read and control cron tasks on remote systems.

Go to Download

An Asterisk component which hooks into the Asterisk Management Interface on remote systems.

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

Quartz Remote Scheduler Bundle

Go to Download

Codeception extension for PhireMock. Allows to stub remote services for HTTP requests.

Go to Download

FileSharing as Upload/Download to local/remote storage for Lararpess CRUD

Go to Download

Validate e-mail addresses by connecting to the remote MX server.

Go to Download

A flexible FTP and SSL-FTP client for PHP. This lib provides helpers easy to use to manage the remote files.

Go to Download

ISPConfig Remote Api SDK

Go to Download

Integration of the standalone server for resizing and converting remote images

Go to Download

Library for collecting local and remote system performance statistics

Go to Download

Package to manage remote configuration parameters in PHP.

Go to Download