# rvm Published articles for rvm. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells DevFeed: [Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-20T09:36:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Shell](), [Command-line interface](), [Bash](), [Zsh]() Tags: [bash](), [command](), [nushell](), [rails](), [ruby](), [rvm](), [shell](), [zsh]() ### AI overview The author explains that they can continue using NuShell as their main shell while switching to Bash or Zsh when tools such as RVM require them. A Rails project is successfully created after switching to Bash. ### Source excerpt I really, really like NuShell. The realization that maybe I had to leave was, I'll admit, mildly crushing. And then I just had the realization that maybe I don't have to leave NuShell and slink back to the dirty, byte infested corners of Bash and Zsh. Here's what just happened: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rails new pool_api --api Rails is not currently installed on this system. To get the latest version, simply type: $ sudo gem install rails You can then rerun your "rails" command. /Users/sjohnson/Sync/coding/flow_analytics/open_source〉ruby -v 07/20/2022 05:34:41 AM ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.x86_64-darwin21] /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rvm use And that was the point when I realized "Oh yeah - RVM doesn't work on NuShell" and then it struck me - I can run Bash: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉/bin/bash 07/20/2022 05:34:57 AM bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/.iterm2_shell_integration.nu: No such file or directory ERROR: Can't find Ruby library file or shared library lunchy usage: dirname string [...] The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. [sjohnson:~/Sync/coding/flow_analytics/open_source] [base] $ rails new pool_api --api create create README.md create Rakefile create .ruby-version create config.ru create .gitignore create .gitattributes create Gemfile run git init from "." ... So maybe my system can mostly run NuShell and I can drop in and out of Bash / Zsh when I need different things. Fingers Crossed. ## Declaring Ruby Bankruptcy, The Ruby Psych 3.1 Issue, RVM and RBEnv DevFeed: [Declaring Ruby Bankruptcy, The Ruby Psych 3.1 Issue, RVM and RBEnv]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-15T06:35:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Ruby](), [Development](), [legacy]() Tags: [errors](), [installation](), [legacy](), [rails](), [rake](), [rbenv](), [ruby](), [rvm](), [zsh]() ### AI overview A developer describes problems after installing Ruby 3.1 with RVM, including missing psych and failures in bundle install, irb, Rails console, rake, and switching Ruby versions. After removing RVM and rbenv, the author plans to use RVM for Ruby 3.1 and later and rbenv for older projects. ### Source excerpt I had a bloody awful Sunday three days ago. I had started work on a new application that had Ruby 3.1 set in its Gemfile and I blithely installed Ruby 3.1 using RVM. And then my life began to suck slimy green toads with errors like this: /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/yaml.rb:3: warning: It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. I'd like to say that I wasn't quite as diligent in fixing this because, well, it was sunday. However, given the readiness by which most of us generally install new versions of ruby, that wasn't it. We simply aren't used to breaking changes with Ruby. The ctrl blog does a great job of describing this. Thank you. The basic issue is that psych is a low level gem and once it changes, well, your world kind of just breaks. What I pretty much found out immediately is that every single thing I wanted to do with Ruby just failed: bundle install irb rails c rake And, "drum roll" - changing over to a different ruby The fact that I couldn't change over to a different ruby basically meant that I was screwed. I don't think that this was intended. And it is entirely possible that this was some kind of whacky interaction on a development system with, ahem, a lot of rubies and crazy legacy conflicts but that is what happened. Declaring Ruby Bankruptcy Since I couldn 't change rubies, everything just devolved into an amazing pool of suckitude. Not only couldn't I use Ruby, I couldn't blog, run any of my utility scripts, etc. My final answer was to declare ruby bankruptcy and: delete rvm delete rbenv delete all references to rvm and rbenv from zsh and other profile files reboot rm -rf ~/.rvm rm -rf ~/.rbenv reboot I've been a long time Ruby user so this process exposed some craziness like 2.3.1 log files owned by root which couldn't be deleted. Taking a Break This was the point where I threw my hands up, walked away an ## Specifying Ruby Version for HatchBox Deployment DevFeed: [Specifying Ruby Version for HatchBox Deployment]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-05-31T11:13:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Ruby](), [Deployment]() Tags: [deployment](), [errors](), [hatchbox](), [ruby](), [rvm]() ### AI overview This article explains how to resolve a Ruby version conflict during Hatchbox deployment by keeping the Ruby version in the Gemfile synchronized with the version in .ruby-version. The author reports that synchronizing both files to Ruby 2.6.2 fixed the issue. ### Source excerpt I recently had the situation where an application that I deployed to Hatchbox failed with a Ruby version conflict: -----> Installing gems... /home/deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated Your Gemfile lists the gem capybara (>= 0) more than once. You should probably keep only one of them. Remove any duplicate entries and specify the gem only once (per group). While it's not a problem now, it could cause errors if you change the version of one of them later. Your Ruby version is 2.5.1, but your Gemfile specified 2.6.2 I dug into the (excellent) online help for Hatchbox and found that you can specify your Ruby version with either the Gemfile or the .ruby-version file. These files, however, serve different functions: Gemfile - tells your application what to use .ruby-version - tells RVM to switch the ruby version on change into the directory In my case I had both and they were different. Synchronizing them both to 2.6.2 fixed the issue entirely. ## When RVM Seems Insane Run bundle install DevFeed: [When RVM Seems Insane Run bundle install]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-05-30T15:31:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Ruby](), [Development]() Tags: [coding](), [development](), [rails](), [ruby](), [rvm]() ### AI overview A Ruby on Rails project reports Ruby 2.6.3 during bundle execution even after RVM selects and verifies Ruby 3.1.0. Running bundle install resolves the mismatch, allowing the Rails console to start under Ruby 3.1.0. ### Source excerpt So I just had this disconcerting moment of weirdness: ❯ rvm use 3.1.0 Using /Users/sjohnson/.rvm/gems/ruby-3.1.0 coding/rails/cartazzi via  v18.2.0 via 💎 v3.1.0 on ☁ (us-west-2) ❯ ruby -v ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin19] coding/rails/cartazzi via  v18.2.0 via 💎 v3.1.0 on ☁ (us-west-2) ❯ bundle exec rails c Your Ruby version is 2.6.3, but your Gemfile specified 3.1.0 What's going on here is: I clearly told the system what ruby to us. I verified it. It told me "OH HELL NO"! This took more than a moment of head scratching and then I hit on it: bundle install And, after that completed: coding/rails/cartazzi via  v18.2.0 via 💎 v3.1.0 on ☁ (us-west-2) ❯ bundle exec rails c Loading development environment (Rails 7.0.2.2) 3.1.0 :001 > ## Use RAILS\_ENV=production in development mode to catch Rails syntax errors DevFeed: [Use RAILS\_ENV=production in development mode to catch Rails syntax errors]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-19T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Testing](), [ci](), [Development](), [Ruby]() Tags: [ci](), [development](), [production](), [rails](), [ruby](), [run](), [rvm](), [server](), [syntax](), [testing](), [trace]() ### AI overview This article presents a Rails debugging and testing workaround for projects without a robust test suite or CI environment. It recommends running the Rails server in development mode with RAILS_ENV=production so syntax errors are caught during startup. ### Source excerpt This is an old school trick that you use when you don't have a robust test suite and / or a CI environment. When you run Rails in development mode it is VERY, VERY forgiving of little details like syntax errors - the type of thing that grind your web server to a hard stop. The trick is to use RAILS_ENV=production in development mode and that causes syntax errors to get caught: RAILS_ENV=production bundle exec rails s -p3169 Here's an example stack trace: 20: from /Users/sjohnson/.rvm/rubies/ruby-2.7.0/lib/ruby/2.7.0/tsort.rb:228:in `block in tsort_each' 19: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/railties-6.0.2.1/lib/rails/initializable.rb:61:in `block in run_initializers' 18: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/railties-6.0.2.1/lib/rails/initializable.rb:32:in `run' 17: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/railties-6.0.2.1/lib/rails/initializable.rb:32:in `instance_exec' 16: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/railties-6.0.2.1/lib/rails/application/finisher.rb:122:in `block in ' 15: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:449:in `eager_load_all' 14: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:449:in `each' 13: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:338:in `eager_load' 12: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:338:in `synchronize' 11: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:346:in `block in eager_load' 10: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:682:in `ls' 9: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:682:in `foreach' 8: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loader.rb:685:in `block in ls' 7: from /Users/sjohnson/.rvm/gems/ruby-2.7.0/gems/zeitwerk-2.2.2/lib/zeitwerk/loa ## Integrating Minitest with Shippable DevFeed: [Integrating Minitest with Shippable]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-02-04T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Testing](), [CI/CD](), [Ruby]() Tags: [continuous-integration](), [coverage](), [guide](), [how-to](), [reports](), [ruby](), [rvm](), [setup](), [testing]() ### AI overview A practical guide to integrating Minitest with Shippable, including configuration for test and coverage reports and a workaround for a Ruby compatibility issue involving RVM. ### Source excerpt I know, everyone uses Travis. I have nothing against it. But in case you want to test and/or use Shippable, this might be just the guide for you. I will also show how to setup those nice tabs with the test and coverage reports.