・ Because the poster is a beginner, he / she may post incorrect information. At that time, I would appreciate it if you could point out without any refraining.
The error happened abruptly, and when I tried rails s
to restart the local server, I got the following error:
Could not find puma-4.3.3 in any of the sources
Run `bundle install` to install missing gems.
I was confused because I didn't remember playing with the Gemfile. Just in case, I checked if there was a change history on GitHub Desktop, but again nothing changed from before the server restarted.
For the time being, there was Run bundle install
, so when I executed it obediently, an error occurred again.
An error occurred while installing puma (4.3.3), and Bundler cannot continue.
Make sure that `gem install puma -v '4.3.3' --source 'https://rubygems.org/'` succeeds before bundling.
The terminal got angry with red letters.
I modified the Gemfile because there was an instruction in the error statement that gem install puma -v '4.3.3'
(puma version should be 4.3.3).
Then I deleted Gemfile.lock and ran bundle install
, it installed successfully and I was able to start the server.
I didn't understand why the error occurred even though I wasn't playing with the Gemfile suddenly, so I did a lot of research on the gem called puma, but I could only find out that it was a web server related gem </ b>. did. It's frustrating, but when the time comes when puma doesn't work again, I'd like to investigate again.
Recommended Posts