Check CI status of the local project

Implements a gateway server to allow barebone basic sensor components to report state change updates as simple via TCP/UDP ports without the 'overhead' of the HTTP protocol. A power sensor for example might just broadcast a four byte floating point binary number once every second to an UDP port or an arduino board sends a UDP datagram whenever a button is pushed. You get the idea, this is how to bring embedded devices into the world of HTTP and Javascript...

A thin and fast web server

A gross and fast web server

Report AMQP messages via Growl. Grr, grr!

Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.

Dedicated to hamsters running in wheels everywhere -> Simple usermode process watcher - stay secure avoid root

A small fast HTTP library and server that runs Rails, Camping, Nitro and Iowa apps.

Sends JSON wrapped data via UDP packets to a given host.

Heartbeat Client in Ruby

Simple scheduled process structure for Rails apps.

A simple hello world gem

Simple utilities for cycling files through the cloud.

...

IdService provides a client and server for setting up a sequential & unique id generation service.

Emergency messaging, application updates, notifier updates, user management & base ActiveAdmin tweaks.

You install this service on a windows machine, and it will keep it's IP address posted to a rails application specified and also updates subdomain status at afraid.org.

Merb plugin that generates daemons

Provides a reliable Object Request Broker and a simple framework for ruby-based services. Jerbil servers run on each machine in the system and share information on registering services. This ensures no single point of failure - machines can come and go (orderly or disorderly) and the network extends or heals as they do. For services there is a parent class that hides all of the jerbil server interactions so that new services can be written without having to write any distributing code. Clients can also be written using an interface that can find one or more services on the network and connect to each or the first. Finally, there are scripts to start and stop the Jerbil server and any Services so that the whole thing can be quickly installed and integrated with your system.

Process background jobs in queue.