Libraries tagged by CHANGE.md
rebib/igo-php
116 Downloads
Morphological analysis engine 'Igo' porting and changed for PHP 5.3 and composer.
rcm/config
2996 Downloads
Extend the functionality of ZF2 config as well as allow config sources to be changed
pointeger/magento2-module-attribute-lock
1 Downloads
The product attribute lock extension enables users to make product attributes read only on product edit page by an attribute configuration. This feature helps the admin to lock a value of product attribute so the value cannot be changed.
piurafunk/docker-php
8 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.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..." } ```
php-libs/value-states
107 Downloads
Extends php-libs/observer to track if a values have been initialized or modified (changed after initialization)
o3-shop/o3-shop
477 Downloads
This file should be used as an O3-Shop project root composer.json file. Entries provided here intended to be examples and could be changed to your specific needs.
nsp-code/wp-hide
1 Downloads
Hide and increase Security for your WordPress website instance using smart techniques. No files are changed on your server.
nitro2010/phpqrcode
27 Downloads
PHPQRCode porting and changed for PHP 5.3 compatibility
nakatsinho/mpesa-php
8 Downloads
This is the latest simplified way to embed Mpesa payments in your PhP application, and I'm doing remake from abdulmueid/mpesa package, where I have only changed the required php version.
mygento/ordercommentuser
3232 Downloads
Magento extension that provides ability to see who changed order status
mygento/order_item_catalogrule
2209 Downloads
Magento extension that provides ability to see who changed order status
mygento/module-order-comment-user
4704 Downloads
Magento extension that provides ability to see who changed order status
musahmusah/password-change-notification
0 Downloads
A simple laravel package to send mail notification to the user when their password is changed.
mjahn/last-updated-at-behavior
37 Downloads
A behavior allowing you to generate a last changed column calculated from all related tables with a column updated_at for Propel2.
maxvaer/docker-openapi-php-client
4 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.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..." } ```