konstantinhaase

4 ms·

1. 1.▲
   Travis CI moves to Blue Box(bluebox.net)

   2 points by konstantinhaase 14y ago|0 comments
2. 2.▲
   by konstantinhaase 14y ago

   I would actually say that Travis CI is a Rails app, Rails is just not taking care of HTTP, but we use large parts of the Rails stack in many of our applications (Travis CI is a fully distributed app). Our API app used to be a Rails applicat
3. 3.▲
   by konstantinhaase 14y ago

   For starters, I would use Sinatra where you use Rack. It takes care of a lot of unknowns for a lot of people. For instance, it makes sure you do proper redirects. Did you know that IE9 implements 302 like 307 but only for redirects from Aja
4. 4.▲
   by konstantinhaase 14y ago

   Travis CI uses Sinatra and it's all but light.
5. 5.▲
   by konstantinhaase 14y ago

   The upgrade process is pretty smooth, the latest Sinatra release still runs all the first example apps published in 2007. Also, the Sinatra code base is pretty small, so just because it's no longer officially maintained doesn't mean you can
6. 6.▲
   by konstantinhaase 14y ago

   Simply run with -o 0.0.0.0, I think the number of people running without firewall or having an annoying firewall warning every time they start a Sinatra process is larger than the number of people developing on a VM. Also note that this has
7. 7.▲
   Success Rate by Programming Language(twitter.com)

   1 points by konstantinhaase 14y ago|0 comments