Whilst investigating https://github.com/shakacode/shakapacker/issues/408 I couldn't quite replicate the issues but did notice there a few places in the code where we were not respecting SHAKAPACKER_CONFIG env variable. This moves it up one level to main Shakapacker::Instance so it should be used consistently.
There are places like runners where we were using configuration object directly but they were already accounting for path set by env variable.
Summary
Whilst investigating https://github.com/shakacode/shakapacker/issues/408 I couldn't quite replicate the issues but did notice there a few places in the code where we were not respecting
SHAKAPACKER_CONFIGenv variable. This moves it up one level to mainShakapacker::Instanceso it should be used consistently.There are places like runners where we were using configuration object directly but they were already accounting for path set by env variable.