Libraries tagged by php map generator
composer/class-map-generator
41546901 Downloads
Utilities to scan PHP code and generate class maps.
bensquire/php-static-maps-generator
1574 Downloads
A PHP library to generate Google Static Map Links.
tidusvn05/google-static-map-generator
8338 Downloads
PHP Wrapper Lib to use google static map generate image file or url
stimulsoft/reports-php
2975 Downloads
Stimulsoft Reports.PHP
netzmacht/php-leaflet
22636 Downloads
PHP leaflet definition and javascript generator
chillerlan/php-imagetiler
3039 Downloads
An image tile generator. PHP 7.4+
christianessl/landmap-generation
2649 Downloads
Generate pixelated, random world maps in PHP.
fedik/php-maptiles
22 Downloads
Simple Map Tiles Generator. Allow to make a Map Tiles with PHP and Imagick.
php-etl/fast-map-config
5583 Downloads
This library implements the Extract-Transform-Load pattern asynchronously in PHP with the help of iterators and generators
andymac2508/php-site-map-generator
11 Downloads
getwarp/collection
633 Downloads
Framework-agnostic PHP collections
purc/autoloader-class-map
3 Downloads
Autoloader class map generator and autoloader for usage in composer or PHP projects
michaeluno/php-classmap-generator
379 Downloads
A PHP class that generates class maps for autoload.
extalion/php-strict-array
4 Downloads
Generator for generic arrays (vector, map)
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..." } ```