Claudio Poli wrote:
> Jacques Fuentes wrote:
>> This was not the issue for me either. When using bundle install
>> --deployment, everything works just fine, but this is a development
>> server and I do not want gems installed to vendor/bundle. The problem is
>> still with a gem specifying a git
Jacques Fuentes wrote:
> This was not the issue for me either. When using bundle install
> --deployment, everything works just fine, but this is a development
> server and I do not want gems installed to vendor/bundle. The problem is
> still with a gem specifying a git repo and a :ref (does not
Michael Hasenstein wrote:
> No, that wasn't the solution. Simply by ensuring passenger_ruby is
> correct (exists, is correct, is used by passenger) did not solve this
> problem for me - at least not on my laptop dev. system. The same setup
> works on my desktop dev. machine. Same passenger, same
No, that wasn't the solution. Simply by ensuring passenger_ruby is
correct (exists, is correct, is used by passenger) did not solve this
problem for me - at least not on my laptop dev. system. The same setup
works on my desktop dev. machine. Same passenger, same rvm, same app,
same ruby - one w
4 matches
Mail list logo
