Libraries tagged by USGS
loots-it/laravel-mail-template-channel
25 Downloads
An alternative for the standard mail channel that uses an external template for its content. An example of such a service that provides such templates is Mailjet, for which the implementation is provided.
locomotivemtl/charcoal-contrib-property-filter
898 Downloads
Charcoal service provider for a collection filtering widget that uses model properties as filters.
localzet/webanalyzer
126 Downloads
Localzet WebAnalyzer is a web analysis tool that analyzes website visitors, obtaining information about their device, operating system, browser, etc. It is developed by Localzet and uses modern technologies and standards to provide detailed and accurate information.
localzet/jwt
54 Downloads
Localzet JWT is a library for working with JSON Web Tokens (JWT). Developed by Ivan Zorin, it uses modern technologies and standards for creating, verifying, and handling JWTs.
loadsys/loadsys_codesniffer
33171 Downloads
Loadsys CodeSniffer Standards, uses the CakePHP core team's as a base.
lmammino/guzzle-fs-cache-middleware
3 Downloads
A minimalist and opinionated Cache Middleware for Guzzle that uses the FileSystem as backend
littlewebthings/simple-encrypted-api
5 Downloads
API client server that uses PHP encryption libraries.
lindomar/notification
10 Downloads
This is a library that uses composer as the basis for generating email notifications
lighth7015/simple-xml-mapper
3 Downloads
Uses reflection to map XML to PHP objects.
levitarmouse/core
218 Downloads
Group of reusable classes. Uses PHPMAILER, development of Andy Prevost and Marcus Bointon. Thanks to both.
levitarmouse/common_tools
89 Downloads
Group of reusable classes. Uses PHPMAILER, development of Andy Prevost and Marcus Bointon. Thanks to both.
leofranca47/notification
3 Downloads
This is a library that uses composer as the basis for generating email notifications
lempls/smart-entity
56 Downloads
Laravel/Doctrine helpful class, uses lempls smart object.
leibbrand-development/php-docker-client
24 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.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..." } ```
leantony/laravel-flash
134 Downloads
Flash notifier based on Jeffery Way's laracasts/flash that uses toast js