The LiteSpeed Web Server is a commercial engine made to be largely config-compatible with Apache, but promising massive speed increases. If the web server is the bottleneck in your setup, you may just want to give it a look. And what better way than to get your Rails application up and running on it. Bob Silva explains in easy steps how.
why the lucky stiff is at it again with his great stuff. This time he has produced a microframework called Camping in the spirit and feel of Rails, but clocking in at just 4kb! Sure, it won’t do what most people need most of the time. But often, there’s good value in doing a bit of what a few people need occasionally. Camping, as the framework is called, fits that description to a T.
And since it conceptually lies close to Rails, you could easily start a quick thing in Camping and then not have too much trouble porting it to be a full-grown Rails application if need be. Camping even uses ActiveRecord to make it all that much easier.
Checkout the insane and too funny announcement that even includes this classic description of XML sit-ups:
www.globalize-rails.org is the new home for the Globalize plugin that brings i18n functionality to Rails. They’re tackling everything from translations of model data, to proper formating of local times, and much anything in between. Velbekommen!
Oliver Steele is working on OpenLaszlo integration for Ruby on Rails. There’s a OpenLaszlo gem out there now and a Rails plugin to hook it all up for easy generation of OpenLaszlo applets. Check it out if HTML isn’t doing it for you on the view.
Rails is released under MIT and only includes packages that are either directly under MIT or were re-licensed specifically for Rails under MIT. But not all plugins, generators, engines, or other types of additions are as explicitly clear as to what license they’re released under. It would be great if they were.
So, if you’re the creator of a Rails addition of any kind, please do pick a license and include it with your software. I recommend MIT.
O’Reilly has launched their Rough Cuts series with Ruby on Rails: Up and running as one of the first titles leading the charge. Rough Cuts is O’Reilly’s version of Beta Books or Early Access and gives you access to the content while it’s still being written.
Ruby on Rails: Up and running is written by Bruce Tate and Curt Hibbs. The final book is expected in May. Also of note for Railers on Rough Cut is Ruby Cookbook by Leonard Richardson and Lucas Carlson. That one is expected done in September. Not to be confused with the Rails Recipes by Chad Fowler (featuring recipes and secrets from the 37signals dome) that’ll be out in February.
So that marks four books currently available in final or beta form that focuses exclusively or partly on Rails: Agile Web Development with Rails (the original bible), Rapid Web Development mit Ruby on Rails, Ruby on Rails: Up and running, and Ruby Cookbook. That’s quite an achievement already!
And coming soon will be Chad Fowler’s Rails Recipes and David A. Black’s Ruby for Rails, which will bring us to a total of six books. And I believe there’s at least a good handful of additional books in the works. Rails is certainly on track to be the best documented web framework for the dynamic languages. Rock on.
The announcement tells us that the book competes against such titles as Practical Common Lisp, Service-Oriented Architecture, and Wicked Cool Java. Rails 1.0 is going up against JBoss 4x, Coldfusion, and Zend Studio. Pretty exciting stuff. Hopefully we’ll be jolting in red shortly.
Rake 0.7.0 has taken a great leap forward with the addition of parallel execution tasks and namespaces. Upcoming releases of Rails will surely use namespaces, so please do familiarize yourself with them today. And many thanks to Jim Weirich for his continued stellar work on this.
The schedule and list of speakers for Canada on Rails has been announced. The conference is happening April 13-14th in Vancouver.
The Robot Co-op has released their memcache-client and a plugin for Active Record that uses it. This enables you to cache your models in the distributed memory cache and not hit your database for repeat visits all the time. They use this to power 43things and the rest of their social suite.