capistrano / capistrano/bundler
bundle install (bundle 1.16.1, AlmaLinux 8), installs to vendor/bundle
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 233
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Suspect this may be the case for any bundle version older then 2.x,
Gems are deploying to vendor/gems, and not release_path/shared/gems, on AlmaLinux/CentOS/RHEL 8 (Ruby 2.5.4, bundler 1.16.1)
Testing with the commands broken out
bundle config --local deployment true
bundle config --local path /home/webapps/test/shared/bundle
bundle config --local without development:test
(.bundle/config - BUNDLE_PATH: is set to "/home/webapps/test/shared/bundle")
bundle install --jobs 4 --deployment
(.bundle/config - BUNDLE_PATH: is set to "vendor/bundle")
The prior behavior of bundle install --path works as expected though.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the commands in the issue on AlmaLinux/CentOS/RHEL 8 with Ruby 2.5.4 and Bundler 1.16.1, inspecting .bundle/config after each command. Compare the deployment path selected by bundle install --deployment with the expected /home/webapps/test/shared/bundle and the behavior of --path; done means the configured deployment path is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100