gh-pages supports https. It's important for prominent help files to encourage best practices.

* Update dependencies

* Use published version of eslint-config-react-app for development

We dogfood on our eslint-config-react-app by using it as our ESLint config,
but installing it from the local folder causes problems when its peerDependencies
are updated, because npm won't update it unless the version number changes.

Use the published version for dogfooding so it can be installed from npm.

* Added note about env server restart

As discussed in [#870](https://github.com/facebookincubator/create-react-app/issues/870)

* Style nit

* Update instructions on publishing to GitHub pages

* Update README formatting

Fix link to recent version of this guide

* Load environment file via dotenv if .env file is present

* Document loading environment variables in .env file

* Minor doc tweaks

* Move ESLint configuration to a separate package

* Remove the ESLint configuration, moved to eslint-config-react-app

* Update ESLint instructions

* Pin the package versions in eslint-config-react-app

* Add a README for eslint-config-react-app

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update package.json

* Update package.json

* Update production eslint-loader config

* Add the ESLint config to devDependencies of the repo

* Clarify proxy instructions in generated app README

* Add backticks to format text/html as code

With the HTTPS env var set 'true', the dev server will serve over HTTPS.

* Disable contentBase in development

* Document #428

* Document testing

* Update README.md

* Update README.md

* Clarify our recommendations on testing

* Okay, that was too much. :-)

* Add a few more things

Small typo line 572 "becasue" to "because"