process.env variables are not available to config/environment.js on boot about ember-cli-dotenv

[fivetanley]

I have no idea what the right answer is here. I'm open for anything that works! We can bump via semver so we don't break existing user's apps if they're using the carrot or tilde operator in npm. #1 sounds good to me, but I'm not sure the right hook to get it. We definitely need the this.app stuff so we can load the right file based off the app's path.

[zilkey]

OK - I think that PR should do it.

Basically here's what happened (correct me if I'm wrong):

• dotenv loads things into process.env (server keys + client keys)

• this package does an extra step of loading those keys directly onto our environments, so we can do the following without mucking with our config

  export default DS.ActiveModelAdapter.extend({
    host: ENV.ADAPTER_URL
  });
  

• the docs are out-of-date, and so lots of developers probably still have this code:

  // config/environment.js
  module.exports = function(environment){
    return {
      MY_OTHER_KEY: process.env.MY_OTHER_KEY
    }
  };
  

• a recent change made it so that the new, more awesome way still works, but the old set-it-yourself-in-environment-js was broken

If I got that right, then this PR should fix it. It basically allows the old way (from the README) to work, and the new way also still works and still only loads client keys.