Little DSL for interact in a microservice environment

MicroService::Nodes so service instances can communicate

Mountable Rails engine that services microservice clients

Stores MicroService Servers so that installs can be tracked

This is a very basic wrapper for the Microsoft Computer Vision API.

Allows delivery of emails using Microsoft Graph API with OAuth 2.0 client credentials flow

Client for the Microsoft Live REST API

Simple wrapper to access data from the Microsoft Open Government Initiative

Sync middleman content to TapirGO

A redirector, url mangler and webpage interceptor for the Squid HTTP proxy

API client for Midea AC systems

A ruby wrapper for the Midwife HTTP API

Interface for creamery API's

Super tiny and simple ruby-based cms that uses yml for content

MimePost API for sending email. You can find out more about MimePost at [https://mimepost.com](http://mimepost.com). For this sample, you can use the api key `special-key` to test the authorization filters.

This gem is unsupported. Use at your own risk. :)

Api client library for Ruby based on the MindMatch graphql rest api

API for Hive Mind

Mingle 3.3 introduced a new Events API in the form of an "Atom feed":http://www.thoughtworks-studios.com/mingle/3.3/help/mingle_api_events.html. The Mingle team and ThoughtWorks Studios are big believers in the use of Atom for exposing events. Atom is a widely used standard, and this event API style puts the issue of robust event delivery in the hands of the consumer, where it belongs. In fact, we'd argue this is the only feasible means of robust, scalable event delivery, short of spending hundreds of thousands or millions of dollars on enterprise buses and such. Atom-delivered events are cheap, scalable, standards-based, and robust. However, we do accept that asking integrators wishing to consume events to implement polling is not ideal. Writing polling consumers can be tedious. And this tedium gets in the way of writing sweet Mingle integrations. We are addressing this by publishing libraries such as this, which if effective, fully hide the mechanics of event polling from the consumer. The consumer only need worry about the processing of events. Said processing is modeled in the style of 'pipes and filters.'

𝕋𝔼𝕃𝔼𝕏 client