Adds commander CLI, improve remote deployments

[flovilmart]

• Adds support for --config, --port --allowInsecureHTTP
• Adds support for PARSE_DASHBOARD_ALLOW_INSECURE_HTTP
• Adds npm start script for easy deployments
• Adds documentation for running behind HTTPS load balancers

fixes #54

[facebook-github-bot]

By analyzing the blame information on this pull request, we identified @drew-gross, @mnoble and @hallucinogen to be potential reviewers.

[peterdotjs]

nice! could we not reuse the npm run dashboard command rather than use npm start?

[flovilmart]

not really as we 'demonize' with & and watch for changes. that breaks the passed command line arguments as they get passed to web pack :(

The ideal scenario would be to have the built dashboard, and just do node dist/index.js

[peterdotjs]

:( lgtm. We're still referencing npm run dashboard elsewhere like in the blog post but we should consolidate the scripts in future. I'm not sure how useful having watch for config changes will be. And it'll be one less script for devs to think about.

[flovilmart]

I've updated the README to reference it for 'deployments'.
IMHO, webpack is nice, but is a pain when it comes to copy files.
Not sure what the production.config.js is doing now or if it's supposedly functional

[drew-gross]

npm run dashboard still works. Even if we recommend other ways of running, we should keep that one around since it's handy for hacking on the dashboard.

@flovilmart production.config.js builds minified bundles and enables a custom Babel plugin that removes proptypes. It cuts the size of the bundle from 3.2mb to 1.1mb, which is nice.

[flovilmart]

yeah but it don't build a production version in dist/ with the minified that I would use for npm start for example :)

I could add this to web pack so when we run npm run build it creates a dist folder ?

[drew-gross]

Yeah feel free to modify it. I think bundles is the name we should stick with though, no real reason to change it.

[flovilmart]

Good! so bundles/parse-dashboard/...