Travis – a distributed build system

Let us introduce us to Travis. What is Travis? As you can read on Github:

Travis is an attempt to create an open-source, distributed build system for the Ruby community that:

  1. allows open-source projects to register their repository and have their test-suites run on demand
  2. allows users to contribute build capacities by connecting a VM that runs a build agent somewhere on their underused servers

Travis Logo You can and should use travis for your open source projects as an continuos integration system. Travis is an incredible project and helps increase the quality of  lots of Open Source projects. So please head over to travis and setup tests for your ruby, node.js, erlang, … projects. – you can also setup your own instance installing Travis and use it for your private projects.

For more information check out the github page and the getting started section.

We’re really happy to be able to support Travis by sponsoring one of the worker boxes.

btw. Sven, Josh, thanks for mentioning us on your talks at Ruby Lugdunum and Frozen Rails 2011 this year. ;)

Btw.: have you heard about the Awesome Bot Factory? With the Awesome Bot Factory you’re able to create bots for your campfire channel. There is a bot to integrate travis to your campfire chat: simply ask the bot for a given status, like:

Jan travis:status Nerds/NerdPursuit
Choco Bits Bot Nerds/NerdPursuit is stable

Or get notified about your project’s new travis builds.

- Thank you, Travis-CI!

Resources:

Nerds/NerdPursuit

For nerds, from nerds.

We’ve presented this projects a few times at Webmontag Köln and DevHouse Friday Chillout @ Papaya and Millepondo. Now we have about 100 Questions in 14 different Topics (algorithms/ bash/ couchdb/ css/ culture/ flash/ grafix/ html/ http/ javascript/ php/ rails/ regex/ ruby/) . But we’re still missing many.

Beside creating new questions we’re working on an offline game – and hey 9elements brought to us – a real time nerd pursuit game – fuck yeah! (will be linked soon).

Participate and send us as much pull requests as you can!

Locate those Missing Puts!

Do you co workers sometimes forget to remove their #puts; or do you sometimes forget where you put* yours? …


Now you can find them ;D

* Pun intended

Freckly + Freckly App

At Railslove we use Freckle and Pivotal Tracker for our client projects.

We wanted a super simple dashboard that just showed us a list of our Pivotal projects and the total number of hours we’ve worked on that project.

You can find the project over here.

I will eventually get round to writing some decent documentation for it, but to roughly get started:

As an added bonus, I didn’t like any of the existing Ruby library so we bundled the code we were using and released it as a gem. It currently only two of the API calls, mainly because that is all we needed. I do plan on extending the gem to cover the whole API.

Heres a quick run through

Static content in your Rails application

Our heros over at thoughtbot.com blogged about static pages and their newly released Rails engine high_voltage. High Voltage helps you dealing with simple, stupid static content pages that nobody wants but everyone needs. ;) (With static pages I’m thinking of imprint, about us, etc.)

In our projects we had a similar solution but to edit the pages more easily and without the need to deploy the whole application we’re saving the content in the database.

Because the database part was missing in high_voltage but I’ve really liked the idea to extract that feature into a rails engine I’ve created a fork last night.

My fork checks if there is a valid template file in views/pages/ – if not it checks the Database and renders the views/pages/show template.

How to use it?

Installation

script/plugin install git://github.com/bumi/high_voltage.git

Create pages
this is up to you. ;)
You can add static files to your app/views/pages/ directory or create a database entry:

HighVoltage::Page.create(:title => "Hello world", :body => "High Voltage! High Voltage!")

That’s it!

For more information check the original thoughtbot post” – You should follow their blog anyway! – And have a look at the readme.

Hope you like my addons.
What are your solutions for static pages?

Next Page →