Libraries tagged by irstea

Library providing collection classes which you can use instead of SPL data-structures.

Go to Download

Allows using tokens (HashIDs) instead of id in Laravel Eloquent models.

Go to Download

A trait you can apply to Eloquent models to have slugs automatically generated on save. A slight omprovement on martinbean/laravel-sluggable-trait to use underscore (or any other character) instead of dash in slugs.

Go to Download

Use Laravel translations from an excel file instead of php arrays

Go to Download

PHP trait that add methods to load objects instead of creating them.

Go to Download

Override Laravel Auth/Pagination views using Zurb Foundation instead of Twitter Bootstrap.

Go to Download

Help store ownsers to reindex from backend, instead of using command line.

Go to Download

Preview Attachment in message area instead of new tab

Go to Download

Monolog formatter for datadog JSON logs (timestamp instead of datetime and defaults with stacktrace)

Go to Download

Log in with email instead of username, mapping via Postfix virtual users table

Go to Download

A php dagger that chisel out the "seam" for testing by rewrite code instead of using any extensions like runkit.

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

Range to be used instead of pair of values

Go to Download

Locked core dependencies; require this project INSTEAD OF mautic/core-lib.

Go to Download

Locked core dev dependencies; require this project INSTEAD OF mautic/core.

Go to Download