jdickey

$ find . | cpio -pmdu /tmp/foo
1738239 blocks
$ cd /tmp/foo
$ du -hsc .
916M	.
916M	total
$ find .[a-z]* * | wc -l
   27791
$ time find .[a-z]* * -delete

jdickey

Four Generations of spec_helper.rb

This Gist contains four successive versions of the RSpec spec/spec_helper file, as used by a recent project.

1. initial-spec_helper.rb takes the file as output by rails g rspec:install and adds a few TODO comments;
2. spec_helper-with-capybara.rb adds Capybara settings;
3. spec_helper-with-database_cleaner.rb adds database_cleaner settings; and finally
4. spec_helper-with-simplecov.rb adds simplecov settings.

jdickey

# encoding: utf-8

# This file allows you to override various Teaspoon configuration directives
# when running from the command line. It is not required from within the Rails
# environment, so overriding directives that have been defined within the
# initializer is not possible.
#
# Set RAILS_ROOT and load the environment.
ENV['RAILS_ROOT'] = File.expand_path('../../', __FILE__)
require File.expand_path('../../config/environment', __FILE__)

jdickey

SOLVED IT! See this Gist. Original follows:

====

OK, here's where I am: trying to get a bog-simple blog app (adapting Avdi Grimm's Objects on Rails e-book example up and happy. With a few twists, as I explain here.

But I can't spec my routes. Why?

In this Gist:

jdickey

SOLVED IT! See this new Gist.

Original follows:

====

After reading /u/Nitrodist's response to my earlier plea for help, I couldn't make requests for /blog/blog (or /blog/blog/, or blog/blog) work.

However, poking around led to this spec file, where only the first of the three specs fails, producing the output in the second attachment.

jdickey

FINALLY! For the three of you who have been following this epic saga through Gists 9907240 and 9908206, we have finally found the elusive green bar; a mystery wrapped in an enigma disguised as a riddle.

There were two key changes that made this work:

1. The describe group containing the routing spec must have the annotation :type => :routing; and
2. The route I was actually trying to get was /blog/blog.

The fact that get 'index' returns success in the third spec in the file is the most flaming of red herrings I've seen in a long, long time.

Green-bar-inducing code and spec files follow. The routing is unchanged from that quoted in the first Gist.

jdickey

I have two systems on my local network, alpha.local and bravo.local. alpha is a Mac (OS X 10.8.5); bravo is a Linux box (Fedora 20).

1. On bravo, I start gem server -V and get the message Server started at http://0.0.0.0:8808;
2. On alpha, I run gem list --source http://bravo.local:8808, which produces a full list of gems installed on bravo;
3. On alpha, I then run bundle install --gemfile Gemfile_local --jobs 3 --path vendor; it fails with the output

Updating git://github.com/bbatsov/rubocop.git
Fetching source index from http://bravo.local:8808/
Retrying source fetch due to error (2/3): Bundler::HTTPError Could not fetch specs from http://bravo.local:8808/

jdickey

Solved with the gracious help of @jenrzzz on IRC (whom I presume is the same as @jenrzzz on Twitter?

The solution was to change

    @blog = OpenStruct.new(title: blog_title,
                           subtitle: blog_subtitle,
                           entries: [])

jdickey

The Rails convention for associating dependent records has long been dependent on creating circular references between the master and detail record. Following a typical blog-type app, one might see

class Blog < ActiveRecord::Base
  has_many :posts
  # ...
end

and

jdickey

#!/bin/bash --login

RBENV_VERSION = 2.0.0-p481
env
rbenv versions
rbenv exec bundle install --path vendor --jobs 3
RAILS_ENV=test rbenv exec bundle exec rake db:migrate
RAILS_ENV=test rbenv exec bundle exec rake cruise