Releasing new parts of your software daily has so many advantages, that you can't afford to refrain from it:
* making releases a breeze
* faster development
* immediate user feedback
* happy developers

7 steps to continuous deployment

We love Git. At Railsonfire we are currently working on a new version of our platform with lots of new features. For every feature we create a separate Git branch and once it’s done we integrate the feature into the main application. This keeps us from having half-baked features spoiling our service.

http://blog.railsonfire.com/2012/11/27/Git-Database-Branches.html

This is part two of our Amazon blogposts which deals with how exactly we autoscale our infrastructure and what our plans are for the future. You should read Part 1 as well as it lays out why we went with EC2 in more detail.

http://blog.railsonfire.com/2012/11/19/Amazon-auto-scaling.html

When you practice test-driven development, most of the time you need to run only a small number of tests to validate your recent code changes. Unfortunately things change once you start refactoring. Refactoring models implicates your entire application. So in order to keep things from going down the drain, you’ll need to run all (or most of) your tests constantly. And that’s where things get tedious.

http://blog.railsonfire.com/2012/11/15/Speeding-Up-Our-Test-Suite.html

For a good number of months we had our Infrastructure based on Hetzner but due to our service growing and a need to scale dynamically we decided to research cloud platforms and move to the cloud. Additionally we experienced severe networking issues from time to time which forced us to switch.

How and why we switched to Amazon EC2

As the Heroku Cedar stack has no Proxy in front of your Rails application any more static assets have to be delivered through your application. This is very inefficient and keeps your dynos or unicorn workers busy with serving your assets.

This blogpost shows how we use the Asset Pipeline, Compass and Amazon Cloudfront to serve all of our assets fast without sending any requests to our application directly.

Make your website super fast with Asset Pipeline, Sprites & Cloudfront

Railsonfire provides a continuous integration and continuous deployment platform for mobile and web applications.

Unicorn is a ruby http server that starts one master process listening on one port and forks several worker processes. Every incoming client request is handed to a worker by the master and when finished the master returns the result to the client. Thus it only needs to listen on one port, but can work on several concurrent requests. Take a look how!

How to get 4x the performance out of Heroku with Unicorn

Railsonfire provides a continuous integration and continuous deployment platform for mobile and web applications.

Heroku provides a great infrastructure, but using their Gem often feels a little bit clunky. Especially when viewing the Heroku logs or getting into the console typing out all of the commands is time consuming.

Getting efficient when working with Heroku

Railsonfire provides a continuous integration and continuous deployment platform for mobile and web applications.