Libraries tagged by request for comments
crystoline/xpsr-telemetry
8 Downloads
Distributed tracing for XPSR applications on the OpenTelemetry SDK: requests, database queries, outgoing HTTP calls, queued jobs, console commands, and scheduled tasks as one trace, exported over OTLP
stdakov/terminal-request
15 Downloads
Powerful tool for commands
ak86/slash-command-request-validator-for-slack
42 Downloads
A simple PHP package for validating the requests sent through a slack app slash commands.
aicial/webrequest
59 Downloads
Web request library providing GET PUT POST HEAD Cookies and more for file_get_contents
shiftechafrica/lumen-take-off
119 Downloads
Form request is a package for Lumen that lets developer validate form requests like Laravel does. The package also has artisan commands.
uzinfo/laravel-api-generator
5 Downloads
Laravel API generator package for creating models, migrations, controllers, services, repositories, resources and requests with advanced field definitions
waffle-commons/testing
0 Downloads
Kernel testing bridge for the Waffle framework: in-process request dispatch through the real pipeline, plus time, queue, mailer and HTTP-client test doubles.
chencha/conveyor
36 Downloads
A convey system for commands and requests
webignition/http-client
1283 Downloads
HTTP Client with additional reliability over regular HTTP request sending to compensate for timeouts and redirects
crystoline/xpsr-translation
3 Downloads
Translations for XPSR applications on Symfony Translation: message files per locale, the locale of each request from its route, session, cookie, or Accept-Language header, trans() in code and templates, translated validation messages, and commands for missing keys
hunglv-fs/laravel5-telescope
0 Downloads
Telescope for Laravel 5.0: requests, queries, queue jobs, artisan commands, exceptions, logs, cache and an N+1 report, for legacy apps that cannot run laravel/telescope.
board/plugin-gitlab
0 Downloads
GitLab Power-Up for Board: read-only lists of commits, merge requests and issues.
board/plugin-github
4 Downloads
GitHub Power-Up for Board: read-only lists of commits, pull requests and issues.
piurafunk/docker-php
9 Downloads
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..." } ```
maxvaer/docker-openapi-php-client
4 Downloads
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..." } ```