Post History
Actually, in compiler I had marked the Run the script in context of the bundle (bundle exec). When I unmarked it, I noticed I could compile. So, the second problem is solved. I can run Ruby file no...
Answer
#3: Post edited
- Actually, in compiler I had marked the `Run the script in context of the bundle (bundle exec)`. When I unmarked it, I noticed I could compile. So, the <a href="#gem_error">second problem</a> is solved. I can run Ruby file now.
- Actually, in compiler I had marked the `Run the script in context of the bundle (bundle exec)`. When I unmarked it, I noticed I could compile. So, the <a href="#gem_error">second problem</a> is solved. I can run Ruby file now.
- 
- My gem directory was at `/.local/share/gem/ruby/3.0.0`. I had "`Changed Directory`"
- ```
- cd /.local/share/gem/ruby/3.0.0
- ```
- Then, run following commands.
- ```
- gem install bundler
- gem install rails
- bundle install
- ```
- Then, <a href="#rails">first</a> and <a href="#bundle_install">third</a> problem will be solved.
#2: Post edited
Actually, in compiler I had marked the `Run the script in context of the bundle (bundle exec)`. When I unmarked it, I noticed I could compile. So, the <a href="#gem_error">second problem</a> is solved- 
- Actually, in compiler I had marked the `Run the script in context of the bundle (bundle exec)`. When I unmarked it, I noticed I could compile. So, the <a href="#gem_error">second problem</a> is solved. I can run Ruby file now.
- 
#1: Initial revision
Actually, in compiler I had marked the `Run the script in context of the bundle (bundle exec)`. When I unmarked it, I noticed I could compile. So, the <a href="#gem_error">second problem</a> is solved 