If you’re wondering what the right shebang line is when you’re using RVM, it’s:
#!/usr/bin/env ruby
For searchers, it’s also called a hashbang, hashpling, pound bang, or crunchbang.
If you’re wondering what the right shebang line is when you’re using RVM, it’s:
#!/usr/bin/env ruby
For searchers, it’s also called a hashbang, hashpling, pound bang, or crunchbang.
I cloned Objective Resource from the yfactorial ObjectiveResource github repository, initialized the git submodules, and tried building it under the SDK for 4.2.
I ran into two problems when trying to build. First, it complained about not knowing where the SDK was. To remedy this, I went to Project -> Edit Project Settings -> Build -> Base SDK, and changed it to latest. It was originally looking for the 3.0 SDK, which wasn’t installed on my machine.
Trying to change Heroku command-line users to add add-ons for the user in our organization that has the credit card information associated with him (Bill).
My account info: anthony@example.com His account: bill@example.com
Can run this to clear out my current Heroku username and password:
rm ~/.heroku/credentials
But unfortunately even after I authenticate with the new username and password, things don’t quite work right:
Here’s all the stuff I needed to get autotest (formerly known as autospec) working with Rails 3 and rspec 2. I’m assuming you are using bundler.
# Gemfile
source 'http://rubygems.org'
gem 'rails', '3.0.1'
group :development, :test do
gem 'rspec'
gem 'rspec-rails'
group :autotest do
gem 'ZenTest'
gem 'autotest'
gem 'autotest-rails'
end
end
# .rspec
--format nested
--color
# autotest/discover.rb
Autotest.add_discovery { "rails" }
Autotest.add_discovery { "rspec2" }
Then you can run:
Trying to install ZenTest gem, and came upon this error after adding:
group :development, :test do
gem 'rspec'
gem 'rspec-rails'
gem 'cucumber'
gem 'cucumber-rails'
gem 'webrat'
gem 'nokogiri'
gem 'zentest' #######
end
$ bundle install
Fetching source index for http://rubygems.org/
Could not find gem 'zentest (>= 0, runtime)' in any of the gem sources.
The solution was to realize that ZenTest actually capitalizes the gem name. I think this is the only gem that does this that I know of.