The web’s most amazing monitoring service is now available on AppHarbor!
StillAlive is reInteractive's fantastic website feature testing application born out of a simple necessity. There are a myriad of websites that will monitor the uptime of your site, but before StillAlive came along none tested the paths that users take through your website, to make sure that everything is working as intended. Imagine if your online store was responding to pings, but returning a garbled homepage... a computer might not know the difference, but your users sure would! StillAlive is set up to alert you to these problems before your users get a chance to. To find out more about this service, check out our homepage at https://www.stillalive.com.
In a tweet today, David Heinemeier Hansson announced the coming end of support for Ruby 1.8.7 and older.
Rails 3.2.x is planned to be the last 3.x release branch. rails/master is now 4.0.0.beta and will only support Ruby 1.9.3+. Farewell 1.8.7! — @dhh
So as you may know, the long awaited arrival of TextMate 2 is upon, albeit in alpha form. Being the excitable fellow that I can be, I of course jumped on this the absolute moment that I could, closed down my MacVim instance and downloaded TextMate 2. I started it up, and oh no, again I found myself confronted with trailing whitespace that had plauged me all through my TextMate usage. But some talking to other folks I discovered that all was not lost, and I had indeed had the power to rid myself of this, as I had done in the past without knowing it.
In the text bundle there is a command, Remove Trailing Spaces in Document / Selection.
A recent project we have been working on at rubyx required us to design a completely customised shopping cart. It gave me a good opportunity to look at some of the important factors in what makes a shopping cart tick, and the most effective ways in which to communicate what can often be an overwhelming amount of information.
From my broad sweeps of the e-commerce cross-section I selected, there are some examples of excellent, and not-so-excellent, checkouts out there from which to draw inspiration. Of course, the bad examples are usually the best educators, so we'll start there. Plus, train-wrecks are just more fun!
Engines are a new feature within Rails 3 which allows for code such as that found in models and controllers to be shared in gems across applications. You may be familiar with the Devise gem, which is a very advanced engine. In this guide we cover how the foundation for the
foremengine was laid.
A lot of people have been saying there's no real documentation or examples for Rails engines at the moment and that somebody should do something about it. Coincidentally, Rails 3 in Action will (eventually) have a chapter on creating an engine which will go into more detail than this guide, but this guide should help you get set up with an engine, as well as showing one setup of testing which uses RSpec + Capybara.
As our applications become better connected with the net in general, we find we need to communicate with 3rd party services.
If we are lucky, these are clean, well documented, RESTful APIs which make our heart sing. If we are super lucky, they even confirm to what ActiveResource expects, and will be trivial to implement.