CODEWITHSUNDEEP
ruby-on-railsrubyruby-on-rails-3console
tekknolagi
tekknolagi

Reputation: 11022

Run Rails commands outside of console

With my large application, the Rails console takes a while to load up. Is there a way to single commands more easily?

I'd also like to be able to automate stuff, and echo "query" | rails console isn't a great way to do things.

Thoughts?

EDIT: What about a long-running process that I can ping queries to whenever I have need?

Upvotes: 56

Views: 28858

Answers (3)

Tim Peters
Tim Peters

Reputation: 4144

There are two main ways to run commands outside console:

  1. Rake task which depends on :environment

  2. rails runner (previously script/runner), eg:

    $ rails runner "query"

Both are pretty well documented on the rails guide: https://guides.rubyonrails.org/command_line.html#bin-rails-runner

Both of these methods will still take the same time as a console to fire up, but they are useful for non-interactive tasks.

Upvotes: 91

Aviv
Aviv

Reputation: 14527

Solution: bundle exec command allows us to run an executable script in the specific context of the project's bundle - making all gems specified in the Gemfile available to require in Ruby application. In addition it eventually avoids any conflicts with other versions of rake installed globally.

echo '<command>' | bundle exec rails c

for more information look at the documentation of bundler

example:

configuration_item=$(echo 'ConfigurationManager.getKey("authentication_method")' | bundle exec rails c )
echo $configuration_item

#output:
MFA_authentication

Upvotes: 1

mahemoff
mahemoff

Reputation: 46509

Just pipe it in:

echo 'puts Article.count' | bundle exec rails c

It should now be a lot faster than when then the question was originally asked, because of Spring. It's not immediate, but still a lot faster than spinning up the whole app. Use this for the fast lane, it should run in under a second (assuming your required command is fast):

echo 'puts Article.count' | spring rails c

If you really want a single long-running process, you could easily do it by creating a controller action that simply runs whatever you POST to it, then send commands to it using curl behind an alias. The action would of course be completely insecure and should be triple-guarded against running anywhere near production, but it would be easy to setup.

Upvotes: 47

Related Questions