Libraries tagged by properos

Biblioteca com models comuns utilizados nos projetos ZF2.

Go to Download

Biblioteca com classes comuns utilizadas nos projetos com Laminas.

Go to Download

MongoDB PHP library ( modified to use static property for selected server )

Go to Download

This plugin provides structured data for events so Google can index them properly.

Go to Download

Access properties with associative array or object notation seamlessly

Go to Download

Class/method/property metadata management in PHP

Go to Download

Symfony bundle for validation Bitrix elements by property.

Go to Download

Proposal psr-event

Go to Download

Exposer exposes hidden properties and methods

Go to Download

Alternate ReflectionExtractor for symfony/property-info

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

A set of property validators

Go to Download

Provides support for configuring the properties of an object for validation, formatting, and storage.

Go to Download

If you have tried to import PayPal transaction history into traditional accounting platforms such as Mint or QuickBooks you probably discovered it didn't work. This is because PayPal does a lot of unusual things that make their exports incompatible. This application was built specifically to solve that problem. Just upload your script and click download, in seconds you'll have a properly formatted CSV or Excel file ready to be imported into any traditional accounting software.

Go to Download

A more complex way for merging array properties.

Go to Download