If you let the bundler run in the end and then try to change the gemfile, bundler will stubbornly install 1. So once it generates the base for you and you have successfully skipped the bundler in the end, NOW change the line in the GemFile:. You will see that bundler will say bundle complete!
Let me know how it goes - because I did some wicked dragging and dropping of sqlite files and setting paths and whatever and it just kinda worked at one point from now on. If it works for you too - then great! Thanks for the assist-- I'll let you know if I get it to work.
I'm pretty new to learning code, and I feel like I got thrown directly into the deep, dark, shrieking eel-infested end of the pool trying to install RoR. And I also ran into a problem with a key that GitHub wanted-- I got one to generate, but it was in the wrong format I downloaded and installed Ubuntu to give the Linux platform a try, and kept running into walls there as well.
I have learned quite a bit trying to unknot everything, so at least there's that, right? This worked for me, but you have to have Git for Windows installed and use Git to enter the code. It won't work from Windows Command. Also, before attempting this, I deleted the previous "blog" directory and started fresh. I just went into windows and clicked delete. No big deal. Once you have your new blog folder, Windows won't know how to open the gem file so you have to double click it select a program, or right click and choose "open with.
Total noobs like me probably won't know this. I just thought "Ah, shit, well, lemme try Atom, that's made for coders so maybe it'll work on this Thornybastard thanks for the heads up on the Git for Windows. However, I ran into an issue there too. So I had the same problem first day with bundle install at sqlite3 1. I was directed to this thread and tried the solutions. So the multiple step process which threw different errors at each stage has led back to the original error at what should have been the final step.
No double gem over here. Yes using Git bash. No not using a VPN. Rails 5. Cheers for the attempt, anyway. An error occurred while installing bootsnap 1. Make sure that gem install bootsnap -v '1. An error occurred while installing sqlite3 1. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. The text was updated successfully, but these errors were encountered:. Hi ravigupta, I had the same issue. Since it seemed that the RailsInstaller was somewhat old, I decided to deinstall everything and delete all the folders and to restart from scratch.
Sorry, something went wrong. I had the same issue. Total 90 delta 6 , reused 0 delta 0 remote: Compressing source files Warning: Multiple default buildpacks reported the ability to handle this app.
The first buildpack in the list below will be used. Try 'brew install sqlite3', remote: 'yum install sqlite-devel' or 'apt-get install libsqlite3-dev' remote: and check your shared library search path the remote: location where your sqlite3 shared library is located. Check the mkmf. You may remote: need configuration options. Failed to install gems via Bundler. Detected sqlite3 gem which is not supported on Heroku: remote:! Push rejected, failed to compile Ruby app. Push failed remote: Verifying deploy Push rejected to murmuring-river Improve this question.
Add a comment. This will install the sqlite-related packages required by Rails on RedHat and Centos : sudo yum install sqlite sqlite-devel. Jim U Jim U 3, 1 1 gold badge 11 11 silver badges 23 23 bronze badges. This works for me. Omar Omar 81 5 5 bronze badges. Sign up or log in Sign up using Google.
Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.
Linked Related Hot Network Questions.
0コメント