Every repository with this icon (
Every repository with this icon (
| Description: | A Rails project template, intended to keep app baselines up to date. Includes shoulda, mocha, factory_girl, Hoptoad, git rake tasks, cap recipes, etc. edit |
-
1 comment Created 7 months ago by thoughtbotmake test/shoulda_macros better or removefeaturexWe've tried a few better approaches for testing will_paginate, for instance. Also, the should_have_form is weak.
Comments
-
The application layout uses PROJECT_NAME.humanize. We should either remove this or set PROJECT_NAME in environment.rb during script/create_project
Comments
-
Reported by Dan Croak
Add validates_email_format_of to vendor/gems:
Comments
-
0 comments Created 5 months ago by dancroakAdd Pages Controller for static contentfeaturexComments
-
and maybe Cucumber. Cuke has binary dependencies, however.
Comments
-
I don't like how create_project always creates your new project in the same directory as you installed suspenders. How does it know that's where I want it? What if I did something you didn't expect like installed suspenders to my ~/bin dir or what if I organize my rails apps by client or something and I want to specify the directory where the new app should be created?
So I propose that create_project be made to accept a path to the app you want to create, just like the rails command it is designed to replace does:
Usage: rails /path/to/your/app [options]I propose that a --base-dir option (and SUSPENDERS_BASE_DIR environment variable) be added to let you change the default base directory.
I propose that a --template option be added to use a repository other than git://github.com/thoughtbot/suspenders.git. I used this to point it to my development repository on localhost for testing. It could also be used if you had made some customizations to the template that you wanted to be used.
I propose that a --user/--password option be added so that the config/database.yml that gets generated actually works "out of the box". One reason this is important is so that the 'script/generate clearance' step doesn't fail.
The only way I was even able to know that that step had failed was by adding a "verbose" option which caused the output of that command to be displayed:
Running 'script/generate clearance'
Access denied for user 'root'@'localhost' (using password: NO)So I propose a --verbose option for users that want to see what's going on behind their backs. Actually, perhaps this should be the new default (and a --quiet option added to suppress it).
Why? Because some commands produce output that give further instructions for finishing the installation:
Ok, enough fancy automatic stuff. Time for some old school monkey copy-pasting.
script/generate clearance, for example, gave this instructions, which the user otherwise would not see:
1. Define a HOST constant in your environments files.
In config/environments/test.rb and config/environments/development.rb it can be:
...By making these options env variables, you can set them once in your .bashrc and forget about them. Or you can use the normal CLI options for one-off switching of options.
The changes I have described are available in my GitHub fork of this project.
Comments
Here's a link to my commit: http://github.com/TylerRick/suspenders/commit/df45fcd2044212243d3ad352e34618c8630d8a18
-
rake default fails saying it could not find a gem that is vendor'd
1 comment Created about 1 month ago by mikewafter creating a project using suspenders and without doing a single thing,
rake defaultwill fail reporting it could not find a gem (in my case, term-ansicolor). of course installing the gem using the standardgemcommand works, but doesn't that defeat most of the purpose of frozen gems?Steps:
./script/create_project bug cd ../bug rake db:migrate # for clearance rakewill fail with:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -I"lib:test" "/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -I"lib:test" "/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -I"lib:test" "/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -I "/Users/mike/Work/rails/bug/vendor/gems/cucumber-0.3.11/lib:lib" "/Users/mike/Work/rails/bug/vendor/gems/cucumber-0.3.11/bin/cucumber" --format progress features/password_reset.feature features/sign_in.feature features/sign_out.feature features/sign_up.feature /Library/Ruby/Site/1.8/rubygems.rb:827:in `report_activate_error': Could not find RubyGem term-ansicolor (>= 0) (Gem::LoadError)meanwhile it seems the gems are detected just fine using
rake gems RAILS_ENV=cucumber- [I] RedCloth >= 4.2.2 - [F] mislav-will_paginate ~> 2.3.11 - [F] thoughtbot-clearance >= 0.8.2 - [F] justinfrench-formtastic ~> 0.2.1 - [F] thoughtbot-paperclip >= 2.3.0 - [F] rack >= 1.0.0 - [F] thoughtbot-factory_girl >= 1.2.0 - [F] polyglot = 0.2.6 - [F] treetop = 1.2.6 - [F] polyglot >= 0.2.5 - [F] term-ansicolor = 1.0.3 - [F] diff-lcs = 1.1.2 - [F] builder = 2.1.2 - [F] cucumber = 0.3.11 - [F] term-ansicolor >= 1.0.3 - [F] treetop >= 1.2.5 - [F] polyglot >= 0.2.5 - [F] polyglot >= 0.2.5 - [F] diff-lcs >= 1.1.2 - [F] builder >= 2.1.2 - [I] nokogiri = 1.3.3 - [F] webrat = 0.4.4 - [I] nokogiri >= 1.2.0 I = Installed F = Frozen R = Framework (loaded before rails starts)Comments
I have exactly same issue here. I went ahead and installed treetop and term-ansicolor globally, and cucumber features pass fine after that. But installing those gems globally defeats the purpose of frozen gems installed in vendor folder. Is there anything I can do to help fix this issue?
-
create_project needs to determine OS that its running on
0 comments Created 17 days ago by ghfuchsThe base_directory variable is formated for Unix style 'mkdir' and 'chdir' commands with '/' slashes.
Needs to base formatting on OS (Unix '/' or DOS '')
Comments












+1 for removing should_have_form and getting assert_contains and assert_have_selector in