Proposal 1: For config in kraken

gistfile1.txt

// make a config object use a confit factory in order to merge two configs


exports.create = function create(options) {
    var deferred, protocols, baseFactory, appFactory;
    deferred = q.defer();
    protocols = createHandlers(options);

    //create a baseFactory
    baseFactory = confit({ basedir: path.join(path.dirname(__dirname), 'config'), protocols: protocols });
    baseFactory.create(function(err, config) {
        if (err) {
            deferred.reject(err);
            return;
        }
        //create App Factory
        appFactory = confit({basedir: path.join(options.basedir, 'config'), protocols: protocols });
        
        //feed appFactory into config from baseFactory
        config.use(appFactory, function(err, conf) {
            //config returned has the final merged object
            if(err) {
                deferred.reject(err);
            } else {
                deferred.resolve(conf);
            }
        });
    });
    return deferred.promise;
};

//I had to change confit to implement use a little differently...
//I know this is a bad practice of the same function acting async as well as sync...
//need to fix that or separate out the different kinds of usage

  use: function use(obj, callback) {
      if (callback) {
          obj.create(function (err, data) {
              if (err) {
                  callback(err);
                  return;
              }
              data.use(store);
              callback(null, data);
          });
      } else {
          common.merge(obj, store);
      }
  }

This solves only the scanning config and {env} .json cases
Still need to solve
[ ] Reference to other files which loads config
[ ] Reference other configs from a config