Libraries tagged by string case

substitute/substitute

0 Favers
168 Downloads

String replacement based template engine

Go to Download


dsjsdz/signatory

0 Favers
6 Downloads

Convert some data of Array to a base64 string and encrypt it.

Go to Download


vigstudio/laravel-avatar

1 Favers
139 Downloads

Turn name, email, and any other string into initial-based avatar or gravatar.

Go to Download


shahrestani/avatar

0 Favers
5 Downloads

Turn name, email, and any other string into initial-based avatar or gravatar.

Go to Download


jsonplus/qtranslate

0 Favers
23 Downloads

an JSONplus extension to provide i18n support to human-readable strings like markdown based upon the qTranslate syntax

Go to Download


brentkozjak/hash-identify

2 Favers
38 Downloads

Identify a hash algorithm based on string input

Go to Download


novay/laravel-avatar

1 Favers
478 Downloads

Turn name, email, and any other string into initial-based avatar or gravatar.

Go to Download


mouf/utils.log.filter-logger

0 Favers
5 Downloads

This package contains a class that acts as a logger. It purpose is to apply a filter on logs and forward the logs to another logger that will take care of storing the log.

Go to Download


volcy/translator-core

0 Favers
20 Downloads

Framework-agnostic Blade string extraction and JSON-based translation catalog.

Go to Download


piurafunk/docker-php

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

Go to Download


maxvaer/docker-openapi-php-client

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

Go to Download


llegaz/redis-cache

3 Favers
658 Downloads

PSR-16 and PSR-6 implementations based on Redis Strings and Hashes

Go to Download


jord-jd/fuzzy-events

1 Favers
3 Downloads

Perform actions based on fuzzy string matches

Go to Download


gevorgmelkumyan/image-file

1 Favers
59 Downloads

The lib contains ImageFile class that allows to create and save image files provided by base64 formatted stringsencoded strings.

Go to Download


chelout/avatar

0 Favers
242 Downloads

Turn name, email, and any other string into beautiful, initial-based avatar with shadow.

Go to Download


<< Previous Next >>