tddium runs your rspec, cucumber, and test::unit tests in our managed cloud environment. You can run tests by hand, or enable our hosted CI to watch your git repos automatically. Tests run in parallel to save you time, and, if you use Rails, tddium takes care of setting up fresh isolated DB instances for each test instance. Tests can access a limited set of private Selenium RC servers.

Cloud Foundry tooling commands.

Generate trailblazer files from your command file

Enables Vagrant to manage VPS in ConoHa.

Programatically get secrets from Secret Server via the Web Service API

Zool allows you to manage authorized_keys files on servers. It comes with a command-line client 'zool'. The configuration can be done in a pyconfig/gitosis like configuration file. See README.md for further details

Uses the maildir gem to store ActionMailer deliveries.

Build tools

Your favorite collection of themes for alacritty, we initialize with a few themes and you can add more.

Save and load infrastructure configuration

yet another build tool for Visual Studio solutions

Provides a client for making requests and building responses to remote services.

Remote pair programming made super easy

Add a comment summarizing the current schema to the top or bottom of each of your models

AppHealth checks the response for a specific URL on each app server

Upload icon, manifest.json and your app to SFTP server and notify users on updaet using a single command

make puppet installers quicker and more reliable

An assertion for snapshot testing.

`aw` is a command line tool to automate software development workflows based on github pull requests.

Attest allows you to define spec-like tests inline (within the same file as your actual code) which means almost non-existant overheads to putting some tests around your code. It also tries to not be too prescriptive regarding the 'right' way to test. You want to test private methods - go ahead, access unexposed instance variables - no worries, pending and disabled tests are first class citizens. Don't like the output format, use a different one or write your own. Infact you don't even have to define you tests inline if you prefer the 'traditional' way, separate directory and all. You should be allowed to test your code the way you want to, not the way someone else says you have to!