I agree with ddfreynee, but in case you know what you need code can look like: require ‘rake’ Rake::Task.clear # necessary to avoid tasks being loaded several times in dev mode Sample::Application.load_tasks # providing your application name is ‘sample’ class RakeController < ApplicationController def run Rake::Task[params[:task]].reenable # in case you’re going to invoke the same … Read more
You will get what you want by including require ‘ruby-debug’ at the top of your spec: # spec/models/user_spec.rb require ‘spec_helper’ require ‘ruby-debug’ describe User do it “should be valid” do debugger User.new.should be_valid end end You would then run rake spec or rspec as normal NOTE: I now prefer Ruby 2.0+ and pry. It is … Read more
The problem is that Kernel#gets (which is what you’re calling if you just use gets by itself) assumes you’re pulling from a file named by the arguments passed to Rake. That means gets tries to return the content of a file called [rake-task-here], which almost certainly doesn’t exist. Try STDIN.gets.
I think the way rake wants this to happen is with: http://rubydoc.info/gems/rake/FileUtils#sh-instance_method Example: task :test do sh “ls” end The built-in rake function sh takes care of the return value of the command (the task fails if the command has a return value other than 0) and in addition it also outputs the commands output.
Adding include Rake::DSL to the Rakefile before the applications load_tasks were called also worked for me. So in the above user’s case before the DemoApp::Application.load_tasks in the Rakefile.
bundle exec executes a command in the context of your bundle. That means it uses the gems specified in your Gemfile. Much of the time, running bundle exec rake foo has the same results as if you just ran rake foo, especially if you have the same gems installed systemwide as in your Gemfile. However, … Read more
Place it outside the namespace like this: namespace :my_tasks do task :foo do do_something end task :bar do do_something_else end end task :all => [“my_tasks:foo”, “my_tasks:bar”] Also… if your tasks require arguments then: namespace :my_tasks do task :foo, :arg1, :arg2 do |t, args| do_something end task :bar, :arg1, :arg2 do |t, args| do_something_else end end … Read more
Default interpreters from Microsoft are done in a way, that causes them exit when they reach EOF. If rake is another batch file, command interpreter switches to it and exits when rake interpretation is finished. To prevent this write: @echo off cls call rake pause IMHO, call operator will lauch another instance of intepretator thereby … Read more
You’re receiving an encoding error because your filesystem isn’t configured to encode the date you’ve added (since presumably it includes new characters – possibly in your HTML entity encoded map URL – that didn’t exist in your prior data seed). The following will should resolve this error by setting the UTF-8 locale on your machine: … Read more
Rails core team decided to have consistency by enabling rails command to support everything that rake does. For example in Rails 5 commands like db:migrate, db:setup, db:test etc which are part of rake command in Rails 4 are now being supported by rails command. However you can still choose to use rake to run those … Read more