meteor/meteor — pull request #199 by possibilities (2012-06-24 21:07:56+00:00)
Title: Deploy config

Really wanted to automate deployments by responding to github post commit hooks but when interacting with `meteor deploy` via a node.js script (and then a ruby script) I always get this error *stdin must be initialized before calling setRawMode*. Now maybe there's a simple workaround, if so please share w/ me, but I couldn't figure it out and I like the idea of being able to keep my passwords in a config file... hence this patch:

* Generally allows storing config values in a json file that can be used during the deployment process but only a value called `password ` is used right now.

* Will read from config files if `--config` or `-C` is present. Rather than prompting for a password it'll get it from the file.

* Can have a global config at ~/.meteor/deploy.js or a project specific config at ~/.meteor/SITE/deploy.js (or both with the project specific file taking precedence.

If no one else cares for this I'll try 'n work out how to move this behavior to a package.

If core devs like this at all I what do you think of me adding these:

* Warn users when the file is world readable if it has a password value in it

* If there's a file but no password value in it fail to prompting for password