Libraries tagged by irstea

matthewfritz/laravel-cms-scaffolding

3 Favers
43 Downloads

This project contains the boilerplate functionality that you would expect to see in a Laravel CMS. That way you can start working on your cool features instead of having to worry about the routing and content retrieval.

Go to Download


matthewbaggett/docker-api-php-client

0 Favers
6 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.43) is used. For example, calling `/info` is the same as calling `/v1.43/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..." } ```

Go to Download


marten-cz/nette-jwt-user-storage

0 Favers
7 Downloads

Nette IUserStorage implementation using JWT instead of sessions.

Go to Download


marketera/silverstripe-cms-not-required

0 Favers
5 Downloads

This module overrides the SilverStripe CMS in cases where we don't want the CMS installed but dependencies incorrectly require 'silverstripe/cms' instead of 'silverstripe/framework'

Go to Download


manoyeche/imaccessible

0 Favers
32 Downloads

Imaccessible - Adds protection to controller methods instead of routes using list of access provided to user.

Go to Download


mambaru/smtpd

2 Favers
691 Downloads

Fork thefox/smtpd. SMTP server (library) written in PHP. In this fork we use eXorus/php-mime-mail-parser as mail parser instead of zend::message

Go to Download


magneds/messageformat

1 Favers
164 Downloads

ICU message formatting using keywords instead of positional integers

Go to Download


lukasz93p/doctrine-domain-id-types

0 Favers
64 Downloads

Package which allows to use custom interfaces as entities ids instead of primitive types.

Go to Download


liteweb/dotpay

0 Favers
328 Downloads

Package for Dotpay payments via api instead of form

Go to Download


lionmm/compile-blades

3 Favers
154 Downloads

Fork of te-cho/compile-blades to compile blades into a new file instead of overwriting the old file.

Go to Download


liip/drupaleventmanagermodule

2 Favers
1050 Downloads

Event manager to enhance the Drupal hook system (actually use it for you custom events instead of the hook system)

Go to Download


lightningspirit/magic-interfaces

0 Favers
27 Downloads

Provides PHP Interfaces to test some magic methods using instanceof instead of method_exists

Go to Download


leibbrand-development/php-docker-client

0 Favers
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..." } ```

Go to Download


lazarow/elo

0 Favers
2 Downloads

The special function "elo" that can be used instead of the standard "var_dump" method with the "Yakalelo" phrase.

Go to Download


larafun/filters

1 Favers
158 Downloads

Use Filters instead of Requests in your Laravel projects to be more versatile.

Go to Download


<< Previous Next >>