-
Notifications
You must be signed in to change notification settings - Fork 244
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
: ruby ror-installation.md #401
Comments
Bundler by default does not use your locally installed dependencies, but rather "bundles" them in a separate directory. There may be an issue in Fedora let me reproduce that! (I'm a Fedora RoR maintainer). |
I've investigated, and found out that the issue is. It is caused by restriction in the Gemfile.
When on system:
We do not modify the default app, or the dependencies. This needs to be adjusted per-app basis. Please note that this is not the only dependency that's diverged from upstream[*]. Unfortunately, in Fedora, there's still older Puma (but I'm working on [*] We can package only one package version per system, so the upgrades need to be made progressively, not to break other packages, while executing test suites for all packaged gems (that's why it's hard to update Fedora packages). |
To conclude, it's quite easy to |
@jackorp Feel free to modify the RoR page if you think there's missing something, based on this Issue. I can't see what's there to enhance, as we don't want to document per-rails version dependencies. |
I make all steps, and the end when I put
return this error
Could not find gem 'puma (~> 5.0)' in rubygems repository https://rubygems.org/ or
installed locally.
The source contains the following versions of 'puma': 4.3.6
I check my version of puma and:
[hendrid@fedora app3]$ puma --version
puma version 5.5.2
I don't understand what happened.
To make an app I have to do this:
[hendrid@fedora app2]$ bundle config set --local path 'vendor/bundle'
[hendrid@fedora app2]$ bundle install
and then this
[hendrid@fedora app2]$ rails webpacker:install
The text was updated successfully, but these errors were encountered: