Comments on: Rails App Template

By: BJ Clark

BJ Clark — Fri, 14 Aug 2009 04:49:47 +0000

Yes, there should be!

I haven’t upgraded to 2.3.3 yet, so I’m glad to hear you’ve got it working. When you get the right versions going, can you let me know and I’ll see if I can duplicate it on my machine with those new versions?

Thanks for working this out, and I’m sorry for not replying, I’ve been on vacation.

By: marfarma

marfarma — Sat, 08 Aug 2009 18:14:04 +0000

OK – now we’re cooking with gas!!

rspec was parsing the options — so had to comment out the rspec and rspec-rails plugins, and UPGRADE the cucumber version, which no longer requires rspec.

Then I could restore the scaffold_resource code with it’s original options.

Further, the less gem needed a higher version than specified in the template, as well. I won’t be surprised if several other gems or plugins won’t need a higher version. Of course, once I get it all tested and completely working, I’ll lock the versions down again. Serves me right for running Rails 2.33.

There ought to be a way to specify the Rails version a given template is compatible with …..

By: marfarma

marfarma — Sat, 08 Aug 2009 05:15:09 +0000

OK – further information about the options on the scaffold line — seems to be related to the cucumber / rspec issue described here: http://wiki.github.com/aslakhellesoy/cucumber/troubleshooting The error does seem to run through the rspec code.

I’ll comment rspec out of the environment, and try that scaffod build again — and see what I get.

By: marfarma

marfarma — Fri, 07 Aug 2009 06:37:26 +0000

Well, the specs pass, as all but two features do.

These are the two failing features:

Failing Scenarios:
cucumber features/authentication.feature:6 # Scenario: Signing Up
cucumber features/authentication.feature:27 # Scenario: Scenario: Resetting my password

In each case, the failure is the same:

“When I open the email # features/step_definitions/email_steps.rb:30
Could not find email . “

By: Marfarma

Marfarma — Thu, 06 Aug 2009 23:14:53 +0000

Ok – I managed to get it to run clean.

Needed to replace self.root with @root.split(‘/’).last

Then it choaked on the scaffold_resource … “-s”,”–skip-migration”

I had to lose the -s and switch the double dash in front of skip-migration to a single dash. I can’t figure out why that was a problem, but perhaps it’s related to rails 2.33 or rspec 1.2.8

Now to move on to the final step, where I can run the tests and see if it actually works.

By: BJ Clark

BJ Clark — Thu, 06 Aug 2009 21:52:33 +0000

Try creating a user for Postgresql that is the same as the name of your project. That’s how I usually do it. I can look at extending this to use a specified user.

By: Marfarma

Marfarma — Thu, 06 Aug 2009 18:19:38 +0000

I’m tracking this down — wanted to say that the login tuning rails has superuser priv. From the shell the create user command succeeds.

Don’t understand why the same thing run from inside a rails session would fail.

Any ideas welcome.

By: marfarma

marfarma — Thu, 06 Aug 2009 06:36:25 +0000

I can’t seem to let this go. I’ve abandoned my attempt to convert this template to sqlite — and gone so far as to install postgresql, so I could try the un-hacked one. However, I must not have it configured the same way you do, as I’m getting this:

executing createuser -s /var/lib/postgresql/cccd from /var/lib/postgresql/cccd
rake db:create
FATAL: role “cccd” does not exist
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/postgresql_adapter.rb:950:in `initialize’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/postgresql_adapter.rb:950:in `connect’

when I run it.

Help!

By: Marfarma

Marfarma — Tue, 04 Aug 2009 17:53:54 +0000

Didn’t see your reply.

I’ll try that.

Thanks

By: Marfarma

Marfarma — Tue, 04 Aug 2009 17:52:32 +0000

Please delete my previous comment.

It was inappropriate of me to dump the entire run log on you.

Thanks for posting the template — and I’ll work my way through my errors over time.