Databases
StackOverflow2013
Postsdbo
PORuby: Accessing rake task from a gem without Rails
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby: Accessing rake task from a gem without Rails
    primarykey
    data
    text
    <p>I'm aware that Rake tasks can be defined in a number of places within a Ruby gem:</p> <ul> <li>inside a Rakefile</li> <li>inside <code>tasks/*.rake</code></li> <li>inside <code>lib/tasks/*.rake</code></li> </ul> <p>I've read that the first two should be used when the tasks are to be executed on the gem itself. It seems the third option should be chosen when tasks are desired to be publicly available.</p> <p>There are many tutorials online demonstrating a variety of methods to load Rake tasks from a gem using Rails, namely by utilising <code>Rails::RailTie</code>.</p> <p>However, I'd like to find a way of using a dependency gem's tasks within another gem without needing Rails.</p> <p>Is there a simple solution to this? Would someone be kind enough to describe the proper approach, or outline what approaches would be viable?</p> <h3>UPDATE</h3> <p>I've tried creating a file <code>bin/my-gem</code> to make available on the system for executing Rake tasks from <code>my-gem</code>. I've put the following inside;</p> <pre><code>#!/usr/bin/env ruby require 'rubygems' require 'rake' task=ARGV[0] spec = Gem::Specification.find_by_name('dsi_core') Dir["#{spec.gem_dir}/lib/tasks/*.rake"].each {|file| puts file and Rake::load_rakefile(file)} Rake::Task.clear # Avoid tasks being loaded several times in dev mode Rake::Task[task].reenable # Support re-execution of a task. Rake::Task[task].invoke </code></pre> <p>Some of the content was based on <a href="https://stackoverflow.com/questions/1170148/run-rake-task-in-controller">this SO post</a>.</p> <p>Sadly I'm doing something wrong because upon installing the gem then running <code>my-gem mytask</code> with <code>mytask</code> defined in <code>lib/test.rake</code> then the following is output:</p> <pre><code>/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task_manager.rb:49:in `[]': Don't know how to build task 'mytest' (RuntimeError) from /var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:298:in `[]' from /var/lib/gems/1.8/gems/my_gem-0.0.1/bin/my_gem:8 from /usr/local/bin/my_gem:19:in `load' from /usr/local/bin/my_gem:19 </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USKomodoDave
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORuby: Accessing rake task from a gem without Rails
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORuby: Accessing rake task from a gem without Rails
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORuby: Accessing rake task from a gem without Rails
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for the link, however this is for executing ruby scripts not Rake tasks. It also would provide no support for rake tasks with arguments. I'm hoping to find an explicit `rake gem::task[args]` style execution method.
      singulars
      1. PORuby: Accessing rake task from a gem without Rails
      1. USKomodoDave
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload