WIP: GoDaddy Contributions

[shelbys]

Added support for merging nested and complex data structures in configuration files in order to better support different paths across multiple environments

[slnode]

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

[bajtos]

Hi @shelbys, thank you for the contribution. Few things to improve the next time you submit a pull request (I addressed them myself in #51 and #52 for this time):

• We use 50/72 format for commit messages - wrap the lines at 50/72 chars, use imperative format ('change foo' instead of 'changed foo').
• Create a new feature branch for your changes, that way you can keep the changes isolated from other things you are doing in your master branch and also it makes it safe(r) to rewrite git history.
• When you want to bring in upstream changes to you feature branch, run git fetch upstream && git rebase upstream/master. That way your commits are replayed on top of the current master, there is no merge commit added and the git history remains linear.
• Changes in non-code files like .gitignore should be made in a standalone commit.

In order to land your patch, I need you to sign our CLA first. Just follow the instructions here: https://cla.strongloop.com/agreements/strongloop/loopback-boot

Note that will need the same for other repositories where you contributed pull requests too:

• https://cla.strongloop.com/agreements/strongloop/loopback-explorer
• https://cla.strongloop.com/agreements/strongloop/strong-remoting

[shelbys]

@bajtos - We use node_modules/.bin/mocha to make it obvious that global isn't expected, and to easily copy to command-line for running single and other experiments

[shelbys]

@bajtos - Regarding CLA, GoDaddy already has a master agreement in place

[slnode]

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

[rmg]

@shelbys The flow is based on the signer's GitHub credentials so we can't manually add your account. It would help us out a lot if you could click through the signing process (it's quick, I promise!) at https://cla.strongloop.com/agreements/strongloop/loopback-boot so that we don't get in the habit of ignoring CLA warnings on our PRs.

[shelbys]

@rmg - Done

[altsang]

thx @shelbys ! it's my fault, I told @rmg not to worry about faking out the system and just asking to have it clicked through as the path of least resistance, thx again!