Libraries tagged by new year
earthit/php-project-rewriter
45 Downloads
Creates a new project from an old one, rewriting identifiers as appropriate.
nandan/contact
0 Downloads
Learning new package development
chibifr/language-detector
19 Downloads
A PHP package that detects the language from a string and can learn new languages.
ahmedsaoud31/atheer
59 Downloads
Atheer is a free Laravel Dashboard Development package without learn new way to use an admin panel.
ehough/contemplate
504 Downloads
Template library that uses pure PHP syntax. Nothing new to learn, blazingly fast, and compatible with PHP 5.2+.
prawee/facebook-cookbook
5 Downloads
Learning about new facebook api with your application step by step
iqmal/laravel-faker-generator
8 Downloads
Laravel Faker Generator for Dummies. This package intend to speed up development process by reducing time for new developer to learn faker package and help create a huge number of dummy data for testing purpose
conia/boiler
158 Downloads
A PHP template engine that doesn't require you to learn a new syntax
theshreyas/admin-product-links
1 Downloads
Adds product links in the admin grids wherever required, preventing searching products in new tabs
oxss/m2-order-grid-field
5 Downloads
This module will add the "Coupon Code" column to the admin order grid. This new column will be searchable and filterable.
mehr-als-nix/php-ftp-client
1 Downloads
New FTP Client based on old PEAR Net_FTP
phamxuanloc/php-deprecation-detector
9 Downloads
Analyzer of PHP code to search issues with deprecated functionality in newer interpreter versions.
noscrape/noscrape
2 Downloads
Noscrape utilizes true-type fonts to obfuscate strings and integers, providing robust anti-scraping measures for websites and applications. It generates a new font with shuffled unicodes, making it nearly impossible to reverse-engineer and decipher data without the obfuscation-font.
grcote7/automenu
3 Downloads
Create easily and quickly a new menu and pages. Ideal for PHP learning.
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..." } ```