Skip to content
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

Handle applications that have already vendored their bundle or set a local bundle config #149

Open
dazuma opened this issue May 31, 2018 · 0 comments

Comments

@dazuma
Copy link
Member

dazuma commented May 31, 2018

Received a customer report that a deployed application could not load its bundled gems. Bundler appeared to succeed in installing the gems, but the application could not find them during Bundler.require. This is not certain, but it is possible this was because vestiges of an earlier local vendored bundle (e.g. vendor/bundle and/or .bundle directories) were present in the application directory prior to deployment.

We should investigate what happens in such a case, and make sure the runtime handles it. In particular:

  • If there is a vendored bundle installation already
  • If such an installation is in a nonstandard location (and thus might not get copied over with the app during the docker build)
  • If there are important bundler settings in a local bundler config that need to be preserved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant