Libraries tagged by dtone

This will allow you to quickly move something to cache and then to get it again at a later time if needed. This will purely be done on the disk. It will delete the files use on exit or again on start up of the program. This is mean to quickly store something out of memory and obtain it later again.

Go to Download

A package that helps to solve the active menu problem - An improvement on the wonderful work done by hieu-le/active, it is specifically suited for laravel

Go to Download

A way to install Twig in your CodeIgniter project, heavilly based on work done in http://willmendesnetoprojects.wordpress.com/2013/01/18/codeigniter-twig-composer-uma-boa-ideia/

Go to Download

Série de cálculos usados na Box, some calculations done at Box

Go to Download

Série de cálculos usados na Box, some calculations done at Box

Go to Download

A minimalist, get-the-job-done web framework with an emphasis on testability

Go to Download

This is a lightweight and easy-to-use Laravel package that allows you to manage user roles and permissions in your application with minimal effort. With this package, you can use lots of pre-defined methods for implementing roles and permissions, as well as assign roles to users and check their permissions. This package provides a simple and intuitive way of coding that makes it easy to integrate with your existing application. It also comes with built-in middleware that you can use to protect routes based on user roles and permissions. Whether you're building a small application or a large-scale system, "Simple Role Permission" provides a flexible and scalable solution for managing user roles and permissions. It's perfect for developers who want a simple and lightweight package that gets the job done without any unnecessary complexity.

Go to Download

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

Sending email and SMS is done using this package.

Go to Download

Simple CMS that gets it done

Go to Download

File and directory management in PHP 5.5+ done right.

Go to Download

Getting notes taken - and things done; encouraging application.

Go to Download

The universal JSON-RPC client/server library. JSON-RPC done right!

Go to Download

A basic Get-It-Done Javascript UI toolkit

Go to Download

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