Or, just install it as a sake task, and run it llike:

Installation notes can be found in the README, get it at github: http://github.com/ambethia/git-railed/tree/master

Please fork it, and customize the behaviors to your hearts content (git-merbed?).

Nice.

- Chris Rohde

Assuming, we have 2 users, Alice and Bob.

Now in my controller’s I can just say something like:

Now I don’t have to write any other code to check ownership, AND an admin can
still play with anyone else’s things.

What I’ve done here is added an :exclusive_conditions option to
has_many. It’s not possible to express this idea with the :conditions
option.

Observe:

Will result in SQL like:


SELECT * FROM things WHERE (user_id = 1) AND (your_condition = ‘yes’)


The “(user_id = 1) AND …“ is hard coded. So I can’t say
“(user_id = 1) OR (something_else)“ with has_many without writing out
the entire statement using :finder_sql.

But then if I do that, I lose all the fun proxy methods, preventing me from
doing things like user.things.find</tt> or <tt>user.things.create
which are of course, in the scope of that user.

Here’s the plugin, http://subvert.itred.org/has_many_exclusive_conditions/.

1. They makes me put more code in the controller, and sometimes worse, I’m forced to express model ideas in the controller.

1. They make me put things in the model that should be handled by the controller.

From the Rails API docs:

This is meant to protect sensitive attributes from being overwritten by URL/form hackers.

That’s what the freaking controller is for.

Give me param_protected and param_accessible. Instead of:

I want:

  class CustomersController < Application
    param_protected :customer => [:credit_rating, :etc]
  end

If no one else has done it (I haven’t looked yet), perhaps I will.

require File.dirname(__FILE__) + ‘/../../test_helper’

require ‘ostruct’


	
class BuyerHelperTest < HelperTestCase

  include BuyerHelper

  def test_should_render_latest_posts
    # capture the output of your helper
    html = render_latest_posts(feed_uri)

    @response = OpenStruct.new :body => html, :headers => {“Content-Type” => “text/html”}
    assert_select “table.latest_posts tr” do |rows|
      ...
    end
  end

	
end

If you’re already using a mocking/stubbing library in your tests, you can forgo the OpenStruct stuff (including ‘ostruct’), in favor of just stubbing it out:

<pre>@response = stub(:body => html, :headers => {"Content-Type" => "text/html"})</pre>

For Rails 2.0 you’ll also need to make some adjustments:

<pre>@response = stub(:body => html, :content_type => "text/html")</pre>

Note: I’m working from a Mac (nuala), and didn’t want to jump through the hoops needed to install the dependencies locally, so I installed the needed tool and ran the export from an Ubuntu linux server (goldie) I have access to.

<pre>jlperry@nuala:~$ ssh goldie</pre>

First, I installed the SVN::Core perl bindings.

<pre>jlperry@goldie:~$ sudo apt-get install libsvn-core-perl</pre>

Then, I downloaded SVM a tool for mirroring Subversion repositories.

<pre> jlperry@goldie:~$ wget http://search.cpan.org/CPAN/authors/id/C/CL/CLKAO/SVN-Mirror-0.73.tar.gz jlperry@goldie:~$ tar -zxvf SVN-Mirror-0.73.tar.gz jlperry@goldie:~$ cd SVN-Mirror-0.73/ </pre>

Run the make file, saying “yes” to the questions about autoconfig and dependencies, and “yes” to “Should we try to install the required module(s) anyway?”. Just press ENTER to stuff about UUID state storage and default umask

<pre> jlperry@goldie:~/SVN-Mirror-0.73$ perl Makefile.PL jlperry@goldie:~/SVN-Mirror-0.73$ sudo make </pre>

And install it:

<pre> jlperry@goldie:~/SVN-Mirror-0.73$ sudo make install jlperry@goldie:~$ cd ~ </pre>

Now, lets get ready to do the export.

You need to create an “~/svn” folder, I think you can change the path svm wants to use, but whatver, this worked for me.

<pre>jlperry@goldie:~$ mkdir svn</pre>

Cache our authentication and acceptance of the self-signed https cert from the server before we can sync:

<pre>jlperry@goldie:~$ svn info https://svn.railsrumble.com/paintitred</pre>

<pre> jlperry@goldie:~$ svm init . https://svn.railsrumble.com/paintitred jlperry@goldie:~$ svm sync . jlperry@goldie:~$ svnadmin dump svn/svm > rumble_dump </pre>

Wow, that was easy.

<pre> jlperry@goldie:~$ logout jlperry@nuala:~$ scp goldie:~/rumble_dump . </pre>

Now, make sure you can import your dump

<pre> jlperry@nuala:~$ mkdir tmp jlperry@nuala:~$ svnadmin create tmp/rumble jlperry@nuala:~$ svnadmin load tmp/rumble/ < rumble_dump </pre>

All the above steps worked for me, your mileage may vary. I just wanted to share these tips with anyone else who might be looking to backup their work from this weekend. It was a blast. There’s a lot of good projects in there, and I’m proud of our team for finishing our entire app by the deadline.

Registration has opened for RubyConf 2007 in Charlotte, and with my grandparent’s bed-and-breakfast just an hour away it looks like I’m in for some nice road-trippin-family-visiting-geekin-early-birthday fun in November.

The main complaint I’ve seen so far is from people getting the impression we want to somehow “reimplement” Rubyforge or create another repository for gems or plugins¹. I can’t imagine something like this could be of any real benefit to Ruby, or Rails.

There’s already a list of plugins, There’s all ready rubyforge, there’s this, there’s that. We don’t want to take away from any of that. We want to tie them all together—and make it easy. That’s the most important bit, making it easy. Easy to find. Easy to keep up with. Easy to change.

I think the “forge” in “RailsForge” is causing a visceral reaction in some people, and I understand that. Perhaps “RailsForge” is misleading. It seemed an easy and available choice for a name, but maybe not the best.

—

¹There’s some debate about plugins and gems, or “plugins vs. gems” I should say. I’ve got to say straight up I side with the concept of sharing code between apps using the gems system.

This should NOT be.

I had the ringer turned down last via the volume buttons on the side. Thankfully, I woke up on my own initiative just before the alarm went of. A few minutes later… a faint buzzing on the nightstand. That’s it. At least now I know I can’t rely on it’s alarm for mission critical wake ups. Here’s to hoping this is a bug, not a a “feature”