Ruby DSL-based software provisioning tool

Ruby API Wrapper for DHL API

Ruby API wrapper for DHL eCommerce EU. Currently only supports the Return Connect product. Check [here](https://developer.dhl.com/api-reference/ecommerce-europe/) for more info.

Ruby wrapper for the DHL Express Global API

DHS ia a Rails-Gem, providing an ActiveRecord like interface to access HTTP-JSON-Services from Rails Applications. Special features provided by this gem are: Multiple endpoint configuration per resource, active-record-like query-chains, scopes, error handling, relations, request cycle cache, batch processing, including linked resources (hypermedia), data maps (data accessing), nested-resource handling, ActiveModel like backend validation conversion, formbuilder-compatible, three types of pagination support, service configuration per resource, kaminari-support and much more.

Supports HTTP/2, HTTP/1.X, HTTP proxying, connection pooling, concurrent requests, and lots more

Dialog is a conversational analytics platform. See https://dialoganalytics.com for details.

Communication prototyping platform

A Ruby Client for diandian API

Diary makes it easy to maintain a file based website with template blog posts and pages.

Packages up code needed to pull data from YAML files when seeding, and adds a process log.

A clean way to roll complex dice structures

Dict to open-source'owy agregator słowników.

SDK to access Dimension Data Cloud api'

Lift up your topic to the top in Diesel Forum

Esta gema sirve para realizar una representación de menús dietéticos usando un lenguaje de dominio específico.

package manager updating diff tool

Digester builds consistent MD5 signatures for arbitrary Ruby data structures.

Uses MD5 to digest hashes, and deep sorts any arrays, as well as sorts the keys

Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.