Closed masterkain closed 12 years ago
I have now updated my .rvmrc to the latest RVM templates, just an issue is left:
push: subcontract --rvm "--with-rubies rvmrc" --chdir ../push --signal INT -- bundle exec slanger --app_key xxx --secret xxx --redis_address redis://127.0.0.1:6379/0
Results in a:
18:46:50 push.1 | Unrecognized command line argument: 'bundle' ( see: 'rvm usage' )
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 RUBY: 1.9.3-head FOREMAN: 0.46.0
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://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