...spring binstub --all, your binstubs will be using Spring. bin/rails console bin/rake db:migrate bundle exec rails ... Bundle exec is inconsistent when it comes to spring. Some commands will use...
...it, some won't. bundle exec rails console # starts Spring bundle exec rake # does not start Spring Disabling Spring You can temporarily disable Spring by setting the environment variable DISABLE...
...integration test container you can run your tests export CHROMEDRIVER_URL=http://localhost:9999 bundle exec rspec specs/system/test_spec.rb # You might need to set remove `--headless` from your chromedriver options in...
...Remove version locks in package.json for webpack and webpack-dev-server Install by calling bundle update webpacker and yarn upgrade Update file contents Work through the Webpacker 4 migration guide...
...use it, you first need to wrap the require 'mathn' call (usually by wrapping Bundler.require) like this: # config/application.rb MathnWorkaround.intercept do Bundler.require(:default, Rails.env) if defined?(Bundler) # If you require "mathn...
...you want to require a gem, that is not in the Gemfile of you bundle and therefore not in your loadpath, you need to add the path manually and require...
...rails_root}/tmp/pids/#{w.name}.pid" w.env = {"RAILS_ENV"=>rails_env, 'PIDFILE' => w.pid_file} w.start = "bundle exec rake my_task &" ... end Your Rake task should write its process ID to that...
...this step definition: Then /^debugger$/ do debugger end Make the Ruby debugger work in Bundler projects Bundle the ruby-debug gem into the :development, :test and :cucumber groups. Problems?
...branch: '0.3.x-lts' # for Rails 3.x in your Gemfile, and do a bundle update mysql2 Background mysql2 used to check that the client library used at runtime actually...
:autocmd Syntax * syn match ExtraWhitespace /\s\+$\| \+\ze\t/ TextMate The Text bundle offers a command Remove Trailing Spaces in Document / Selection, which you can call before saving...
...This is not aware of git (i.e., which lines YOU have edited). In the bundle editor, assign it a shortcut like Cmd + Alt + Backspace. Update: Since 9-29-2012, TextMate2...
...roles: :app, only: { primary: true } do run "cd #{current_path} && RAILS_ENV=#{rails_env} bundle exec rails runner 'ScriptRunner.go'" end becomes desc 'Run script' task :script do on primary :app...
within current_path do with rails_env: fetch(:rails_env, 'production') do execute :bundle, 'exec', "rails runner 'ScriptRunner.go'" end end end end There is no :user setting any more...
...different Rubies can be installed at once. When you run ruby or gem or bundler or any other Ruby binary rbenv looks for a file .ruby-version in your directory...
...depends on crass which depends on Ruby 1.9 gem 'cucumber_factory' Run bundle update on any added/changed gem, e.g. bundle update cucumber capybara selenium-webdriver database_cleaner cucumber_spinner
...test;'" failed and exited with 1 during . Rails 2/3 migrations don't work anymore bundle exec rspec spec -- create_table(:users) bundler: failed to load command: rspec (/home/travis/build/makandra/minidusen/vendor/bundle/ruby/2.2.0/bin/rspec) ActiveRecord::StatementInvalid...
So you got this error, even though your Gemfile bundles mysql2: !!! Missing the mysql2 gem. Add it to your Gemfile: gem 'mysql2' or Please install the mysql adapter: `gem install...
...activerecord-mysql-adapter` (mysql is not part of the bundle. Add it to Gemfile.) The reason for this confusing error message is probably that your Gemfile says mysql2, but your...
...the database, import the dump and migrate to the current branch git checkout d4848ad598b2f02cbca7580a2b928d02996abeb4 bundle exec rake db:drop db:create db:migrate psql -f some.dump -U some_user -h...
...database # or geordi dump -l some.dump git checkout master # or your current working branch bundle exec rake db:migrate
...the current app directory). If you do gem install in the current app directory, bundler will have no knowledge of this. What you want to do instead is bundle pristine...
...similar) and proceeds to deploy staging afterwards: alias await-deployment='watch -g git pull && bundle exec cap staging deploy' Note Use at your own risk. You could be deploying code...
...after switching from the asset pipeline to webpack: 01:05 deploy:assets:precompile 01 bundle exec rake assets:precompile 01 Compiling... 01 Compilation failed: 01 yarn run v1.22.5 01 error...
We recommend you disable documentation generation for gem install by default. Note that Bundler won't install documentation, so this advice applies only when installing gems manually.
You can use rake --where task to find the source location that defines task: bundle exec rake --where assets:precompile rake assets:precompile /home/henning/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/precompiled_assets-0.2.1/lib/precompiled_assets/tasks/assets.rake:5:in `block in...
...specs live in spec/shared/library_name. A Rakefile in the project root that lets you run bundler (rake all:bundle) or specs (rake all:spec) on all projects, which pretty colored output...
...even the diff is quite small afterwards. Preparations 1. Find all libraries that are bundled with the asset pipeline. You can check the application.js and the application.css for require and...
...compiling the packs for production and search for a working example: RAILS_ENV=production bundle exec rake assets:precompile. Remember to remove the folder public/packs afterwards. 11. Configure Capistrano and...
Results logged to /home/user/.rbenv/versions/1.9.3-p551/lib/ruby/gems/1.9.1/gems/debugger-linecache-1.1.2/ext/trace_nums/gem_make.out An error occurred while installing debugger-linecache (1.1.2), and Bundler cannot continue. Make sure that `gem install debugger-linecache -v '1.1.2' --source 'https://rubygems.org/'...
...succeeds before bundling. In Gemfile: pry-debugger was resolved to 0.2.0, which depends on debugger was resolved to 1.1.4, which depends on debugger-linecache Fix: Use debugger version 1.1.4:
...runs to merge requests and the master branch, you can write this: tests: script: bundle exec rake tests rules: - if: '$CI_COMMIT_BRANCH == "master"' - if: '$CI_PIPELINE_SOURCE == "merge_request...