Libraries tagged by followup
xitedev/wiretables-money
0 Downloads
Implementing Brick Money on Laravel Livewire and Wiretables can be achieved gracefully by following some best practices
xanpena/amtega-logging
45 Downloads
Useful class to customize log messages in Laravel following Amtega (Xunta de Galicia) standards.
ws-cv-ua/ws-referral-link
9 Downloads
This package for hiding original link and show info about following
wp-psr/message
0 Downloads
The proxy of WordPress Request response following PSR7
wordpress-phoenix/abstract-theme-base
3 Downloads
PHP class to extend when building a WordPress theme allowing you to follow smart theme setup standards.
websoftwares/access-log
11 Downloads
Log PSR-7 http messages using a PSR-3 logger instance following apache2 access log format.
webfactorybulgaria/nestablecollection
506 Downloads
A Laravel Package that extends Collection to handle unlimited nested items following adjacency list model.
waylandace/pact-php
1183 Downloads
Enables consumer driven contract testing, following the PACT foundation principles.
wataridori/blaravel
10 Downloads
A Custom Version of Laravel Framework which completely follows PSR1/2
uzairsaleem309/test-plugin
7 Downloads
A plugin to display data from the following API https://jsonplaceholder.typicode.com/
undf/connection-bundle
459 Downloads
Directed graph implementation to create any connection between two objects (ie. follower/following relation in a social network)
tushar/lazy-routing
12 Downloads
This is a Laravel library package once install you don't need to declare a route for each method instead you follow a normal camel case convention to declare the method name and the route will auto declared for you.
tslol/docker-api-php
2 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.44) is used. For example, calling `/info` is the same as calling `/v1.44/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..." } ```
trunda/php-cors
6 Downloads
PHP implementation of CORS which strictly follows specification by it's OOP model design. It supports Laravel framework applications.
thusk/tibia-map-array-interface
8 Downloads
basic interface to follow to build a tibia map