via Aidan Finn’s blog :

widgEditor is a small simple lightweight editor. It provided basic rich functions such as bold, italics, links, lists, images and headings. Rails integration:

• Download widgEditor and uncompress
• Copy the widgEditor.js file into …/public/javascripts folder
• Copy the widgEditor.css file into …/public/stylesheets folder
• Copy all the images from the widgEditor distribution …/public/images folder
• Include the javascript and css files in your layout file
• Give any text field you want to be an editor field a class of ”widgEditor”

Example:

<%= stylesheet_link_tag 'widgEditor' %>
<%= javascript_include_tag "widgEditor" %>
<%= text_area 'node', 'content', :cols => "50", 
    :rows=>"3", :class=>"widgEditor" %>

mongrel_cluster makes it easy to manage multiple Mongrel processes behind a reverse-proxy server and load balancer such as Pound, Balance, Lighttpd, or Apache.

See also:

• Apache: Scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel .
• Lighttpd: Using Lighttpd With Mongrel
• Litespeed: setting up litespeed with mongrel

Via RedHanded :

Park Place , a clone of Amazon’s S3 (Simple Storage Service.) It’s written entirely in Ruby, with heaps of help from the Camping 4k web framework. Oh, and no SOAP support to speak of.

gem install camping --source code.whytheluckystiff.net
gem install mongrel activerecord
svn co http://code.whytheluckystiff.net/svn/parkplace/trunk parkplace
cd parkplace/lib
ruby parkplace.rb

Great. Your own private S3. Now you can try all S3-based solutions for free.

Lighttpd after version 1.4.9 requires the full path in the “bin-path” part of the lighttpd.conf file. Also from version 1.4.10 you will have CWD in your config files:

"bin-path" => CWD + "/public/dispatch.fcgi" 

So if you have old lighttpd (<=1.4.8) and old rails applications (<=1.1.0) you can have a problems (with existing or just created applications):

• upgrading only the lighttpd, but not the rails (solution: convert relative paths to the absolute ones)
• upgrading only the rails, but not the lighttpd (CWD keyword support is missing in the old lighty versions, solution: remove CMD+ part from the path).

The best solution is maybe:

• convert all paths to absolute ones for the existing applications
• upgrade lighttpd to the latest version (1.4.11 in the moment)
• “freeze” the existing applications (put in /vendor/rails/ the correct rails version files)
• upgrade the rails (no need to do anything when generate new projects)

Rubricks is a new Ruby on Rails based CMS. The demo looks pretty good. For bad luck it’s crashing my Firefox browser everytime I tryed it :( Working with Safari.

The english site is still not fully functional (the registration at least working). If you decide to go with the japanese site , the registration is different for the both sites, so you cannot try both of them with one registration. Heavy Ajax usage – be sure your browser have JS enabled.

2006/04/02 Update: And another Rails-base CMS Eribium (the demo is also available)

Rails 1.1: RJS, Active Record++, respond_to, integration tests, and 500 other things!

The biggest upgrade in Rails history has finally arrived. Rails 1.1 boasts more than 500 fixes, tweaks, and features from more than 100 contributors. Most of the updates just make everyday life a little smoother, a little rounder, and a little more joyful.

Update 29-Mar-2006: if there is a problems with your typo blog: bind it to rails 1.0

Must read articles for everybody, doing RoR systems administration:

• The adventures of scaling, Stage 1
• Questions and answers for Stage 1
• The adventures of scaling, Stage 2
• The adventures of scaling, Stage 3

03-Apr-2006 Update:

• The adventures of scaling, Stage 4

I translated Gorou-san’s page for following Edge Rails (original is in japanese) – link to the edgerails page in english . For me the described method seems like a pretty smart way to stay organized, even on the cutting edge.

FastCGI is difficult to install/manage. Really it is :(

Problem: DHH loves FastCGI. There is so many FastCGI-centric stuff in Rails:

• script/process/ scripts
• the default lighttpd.conf, generated by script/server

Solution: Zed Shaw

First Zed gave as SCGI_Rails – pure ruby, working on *nix (Linux, BSD, OS X) and Windows. Today I found also another way to skip fastcgi pain with Zed’s stuff – Mongrel :

• Using Lighttpd with Mongrel – have interesting tips for using mod_cml (Lua) for cache management
• Playing with Lighttpd, Litespeed, FCGI and Mongrel – some Lighttpd+Mongrel combi benchmarks

And by the way I wrote some notes about the Second Osaka Rails Meeting (Using runit) on the wiki. FastCGI, SCGI, Mongrel notes included.

Interesting lightweight combination will be:

• Camping framework for the MVC
• moo.fx for the Ajax effects

Somebody already done it?