-
Notifications
You must be signed in to change notification settings - Fork 24
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
Issues with multiple ruby projects using rvm #4
Comments
I have now updated my .rvmrc to the latest RVM templates, just an issue is left:
Results in a:
|
You rvmrc seems to be working fine for me. I have had issues installing foreman. For me it seems the latest version of foreman has an invalid gemspec. What versions of ruby, rvm, and foreman are you using for the top-level that is launching all your projects? |
Having the same issue as @masterkain. System info: RVM: 1.11.3 |
Changing the line to this push: subcontract --rvm --with-rubies default-with-rvmrc do --chdir ../push --signal INT -- bundle exec slanger --app_key xxx --secret xxx --redis_address redis:https://127.0.0.1:6379/0 fixes the problem for me. The quotes are not needed, and the RVM command has changed. |
Thanks @swalke16 for getting to the bottom of it. I'll update the documentation. |
Hello,
this is my Procfile that resides in my main project dir:
Now, ../push does use a .rvmrc like this:
The issue here is that everytime I run
foreman start
with thisProcfile
the system will attempt to download bundler and foreman gems for the push project, sometimes only foreman, like in the example below:Any idea? Thanks.
.bash_profile
The text was updated successfully, but these errors were encountered: