Libraries tagged by string generator
codingphase/reference-generator
1070 Downloads
Reference generator for Laravel
animal-avatar/animal-avatar-generator
2 Downloads
Generate deterministic animal SVG avatars from string seeds (PHP + Laravel)
afzalsabbir/slug-generator
50 Downloads
A simple package to generate slug from string for Laravel
webignition/basil-assertion-generator
143 Downloads
Create a basil assertion model from a basil assertion string
webignition/basil-action-generator
142 Downloads
Create a basil action model from a basil action string
thoom/generator
50 Downloads
PHP 5.3 classes used to generate strings such as UUID and alphanumeric
php_modules/sami-tokens
25 Downloads
Random string/token generator
dotmonk/wildling
42 Downloads
Pattern based string generator library and CLI
danielthegeek/rand-gen
13 Downloads
Random string generator for the CodeIgniter framework
fetch/php-securerandom
756 Downloads
Random string and number generator
worthwelle/alphonic
3 Downloads
A library for converting strings into and from phonetic spellings for use over the phone, a radio or other unclear communications channels. Alphonic provides these conversions not only using the standard NATO alphabet, but also various other phonetic alphabets, making it perfect for easily converting strings with historical accuracy.
voral/vinc-file-version-regexp
0 Downloads
An extension for voral/version-increment to update version strings in custom files using regular expressions.
toppy/tweakwise-client
3 Downloads
Tweakwise API. Tweakwise offers differing REST services that can be called from various URLs and separate parameters. Response in XML and JSON format is offered for all services. XML is the default format, JSON format is also possible by adding ‘format=json’ to the call. Parameters are sent along with the query string (GET Request) via the URL. --- Authentication Authentication takes place by means of a unique key valid for each instance. This key is sent along with the particular service immediately after the call and must be placed before any parameters. This key is issued by Tweakwise.
swuppio/randstring
3 Downloads
Generate random string
piurafunk/docker-php
9 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..." } ```