Args are passed down through the call stack. You just need to make sure your top-level task captures all the arguments all of the dependencies require. In your case you’ll want to put first_name and last_name on the send_letter task. Here is an example that shows named arguments defined elsewhere flowing into the dependency (even … Read more
I’m not sure why either works, but if this is Rails and those are Rails models, your tasks should depend on the environment: task :get_roles => [ :environment ] do By depending on the :environment task, it first loads Rails. Also see: What’s the ‘environment’ task in Rake?.
It does if your rake task depends on :environment. i.e, you declare your task like so: task :my_task => :environment do … end
You’re close 🙂 #lib/tasks/defaultuser.rake require ‘rake’ namespace :defaultuser do task :adduser => :environment do … end Note the use of :environment, which sets up the necessary Rails environment prior to calling the rake task. After that, your User object will be in scope.
To fix this in Rails, I’ve found that you can simply add the following line to each section (development/production etc.) of your database.yml file: template: template0 See ActiveRecord/ConnectionAdapters/PostgreSQL/SchemaStatements#create_database for other options.
Rename your file to reindex.rake and it should work. Related: How to build task ‘db:populate’
At first, you shall detach all connections out of database. By default you use the development environment. Then try to reset database with the following: rake db:reset The rake db:reset task will drop the database and set it up again. This is functionally equivalent to rake db:drop db:setup. This is not the same as running … Read more