-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct Ruby version #54
Comments
@dagnyc |
bootstrap-sass 3.2.0.2 |
@algobasket @pankaj9310 thanks guys. I installed 2.5.3 but now once again issues with json -v 1.8.1 and it fails to install. Why is there always a problem with this? It's beyond frustrating. I changed the json version in Gemfile to 1.8.1 but it doesn't compile properly. I also tried just using gem install json which installs json -v 2.2.0 but apparently that version is not compatible. I've done all the "bundle update this" and "bundle update that" stuff. I've done every bundle known to man. Why can't these things just work without loosing hours of time |
and bootstrap-sass-3.2.0.2 is nowhere to be found |
I deleted the Gemfile and Gemfile.lock and then started with new ones from github. Bundle install was then successful and now I can start my daemons but the site doesn't work anymore. It just says "we're sorry but something went wrong". I think there is something wrong with figaro as I got warnings about it during the install about converting strings |
Now I get this: (StructuredWarnings::StandardWarning)** Invoke assets:precompile (first_time) and this: Tasks: TOP => assets:precompile |
Ok so from what I can see, Figaro is working fine (but with a warning). All my daemons can stop/start with no problem. All rake commands work fine except for bundle exec rake assests:precompile That's when I get the error about gzip not closing properly. Now that may have something to do with bootstrap-wysihtml5/b3 not being found. If I can get this resolved I think the site should be ok.. At the moment I still can't load the site in the browser. Just get the same error "we're sorry something went wrong" |
I moved bootstrap-sass-3.2.0.2 from ruby 2.2.0 to ruby 2.5.0. Compiling gets a little further but now I have a different error: Sass::SyntaxError: File to import not found or unreadable: bootstrap-wysihtml5/core-b3. |
I found out that bootstrap-sass 3.2.0.2 and 3.2.0.3 were yanked due to a vulnerability introduced by a rouge github commit. In it's place version 3.2.0.4 was released but now doesn't have b3.js or core-b3.js how can we resolve this? @algobasket |
So I tried to revert back to 2.2.2 but now it's all messed up and can't complete the bundle install. Too many gem compatibility issues. The peatio installation is completely torched. I had peatio working fine with 2.2.2. Now it's all gone. All that work and hours, days, months of my life gone. Thanks |
Hi @dagnyc , did you find a solution? |
rbenv install -v 2.2.1 | rbenv install -v 2.2.2 | rbenv install -v 2.2.7 |
@algobasket why does this document say to use ruby-2.2.2 https://github.com/algobasket/PeatioCryptoExchange/blob/rebuild-peatio/doc/deploy-production-server.md
but
this document says to use ruby-2.3.0 https://github.com/algobasket/PeatioCryptoExchange/blob/rebuild-peatio/doc/setup-local-ubuntu.md
Which is the correct version to use?
The text was updated successfully, but these errors were encountered: