Development Headquarters

1. Create the symlink from the Rails project's public folder to a location under your document root. I used the ~/Sites folder as my document root. In it, I made the symlink to my Rails project's public folder, like:

cd ~/Sites
ln -s /Users/hg/Developer/Rails/railsproj1/public ./railsproj1

<VirtualHost *:80>
  ServerName localhost
  DocumentRoot /Users/hg/Sites
  <Directory /Users/hg/Sites>
    AllowOverride All
    Options Indexes FollowSymLinks MultiViews
    Order allow,deny
    Allow from all
  </Directory>
  RailsBaseURI /railsproj1
  RailsEnv development
</VirtualHost>

config.action_controller.relative_url_root = "/railsproj1"

Restart Apache and you should be good to go.  Let me know if you have anything to add.

require 'find'
class PopulateRights < ActiveRecord::Migration
  def self.up
    controller_directory = "#{RAILS_ROOT}/app/controllers/"
    controller_files = []
    controllers_and_actions = []
    Find.find(controller_directory) do |node|
      if FileTest.file?(node)
        controller_files << node.gsub("#{controller_directory}","")
      end
    end
    controller_files.each do |controller_file|
      if controller_file =~ /_controller/
        controller_path = controller_file.gsub("_controller.rb","")
        controller = controller_file.camelize.gsub(".rb","").gsub("/","::")
        actions = []
        (eval("#{controller}.new.methods") - (ApplicationController.methods + Object.methods + ApplicationController.new.methods - ["new"])).sort.each do |action|
          actions << action
        end
        controllers_and_actions << { :controller_path => controller_path, :actions => actions }
      end
    end
    controllers_and_actions.each do |controller_actions|
      controller_actions[:actions].each do |action|
        Right.create(:name => action.titlecase + ' ' + controller_actions[:controller_path].titlecase, :controller => controller_actions[:controller_path], :action => action)
      end
    end
  end

  def self.down
    Right.find(:all).each do |right|
      right.destroy
    end
  end
end

require 'find'
controller_directory = "#{RAILS_ROOT}/app/controllers/"
controller_files = []
Find.find(controller_directory) do |node|
  if FileTest.file?(node)
    controller_files << node.gsub("#{controller_directory}","")
  end
end

controller_files.each do |controller_file|
  if controller_file =~ /_controller/
    controller = controller_file.camelize.gsub(".rb","").gsub("/","::")
    puts controller
    (eval("#{controller}.new.methods") - (ApplicationController.methods + Object.methods + ApplicationController.new.methods - ["new"])).sort.each do |action|
      puts "\t#{action}"
    end
  end
end

<%= debug(request.env) %>

<table>
  <tr>
    <th>key</th>
    <th>value</th>
  </tr>
  <% for item in request.env %>
    <tr><td><%= item[0] %></td><td><%= item[1] %></td></tr>
  <% end %>
</table>

Asset Archive Page Type

I like the fact that page_attachments associates assets with a page. (I also like that it uses attachment_fu, for stability reasons.) It would be nice to have a new page type called, say 'Asset Archive'. You could create 'Asset Archives' with familiar names, such as: 'Files' or 'Images'. Also, this extension would add tags, shortening the syntax for retrieving assets, something like:

<r:asset:image from='/files' name='coolpic.jpg'/>

Pagination

This maybe already exists.  But an extension using will_paginate would be welcome.

Here are my de Tocquevillian impressions of Radiant extensions so far.  I'm only rating the ones that interest me.

(I'll be explaining the grading system later.) 

page_attachment - A

sphinx_search - F

reorder - A

paperclipped - A

copy_move - A

Here are a couple of ways of installing a Radiant extension.  It's the page_attachments extension.

Method 1 - The new way

(in your project directory)

cd ~/my/radiant/project/directory

script/extension install page_attachments

Method 2 - The manual way

If installing the extension on a per-project basis, then do:

(as project owner)

cd ~/my/radiant/project/directory

git clone git://github.com/radiant/radiant-page-attachments-extension.git vendor/extensions/page_attachments

rake radiant:extensions:page_attachments:migrate RAILS_ENV=production

rake radiant:extensions:page_attachments:update RAILS_ENV=production

If installing the extension for all projects, then do:

(as root)

cd /Library/Ruby/Gems/1.8/gems/radiant-0.6.9

git clone git://github.com/radiant/radiant-page-attachments-extension.git vendor/extensions/page_attachments

(as project owner)

cd ~/my/radiant/project/directory

git clone git://github.com/radiant/radiant-page-attachments-extension.git vendor/extensions/page_attachments

rake radiant:extensions:page_attachments:migrate RAILS_ENV=production

rake radiant:extensions:page_attachments:update RAILS_ENV=production

We've started learning the Radius tagging language used in Radiant CMS.  Although the language's complete documentation is readily available from Radiant's page editing interface (as a HUD-style Javascript window), I haven't found this documentation anywhere else on the internet yet.  That is, until now.