* Indicate production with NODE_ENV
* Use local.json config to point to Bitwarden production APIs
* Add proxy configuration to cloud and qa environment
* Move notifications to urls
Co-authored-by: Hinton <oscar@oscarhinton.com>
* Set environment URLs in webpack config.
* Provide non NULL dev server
* QA env uses the pq TLD
* Include icons in qa env
* Move base configs to develop.
local configurations should be done in the `./config/local.json` file.
* Fix config override loading to default to development
* Standardize url formatting
* Limit QA settings to those set in production
* Set self hosted in a config
* Specify cloud instead of production
Self hosted and cloud are both production environments.
The ENV setting is used to specify the env type while
NODE_ENV specifies whether development error handling and services.
* Update config instructions
* Remove invalid json
* Change env `production` references to `cloud`
* Fix formatting
* adding in initial config files
* working config files
* updating the client config pattern to default to dev instead of prod
* updating the npm script commands and docs
* Adding a helpful debugging log for the webpack build
* adding in more supporting documentation for running against production
* updating README.md and removing the unneeded ENV var
* Noted upper limit of Node.js verion support for the application: the SCSS dependency v4.13.1 only supports Node.js up to v13.9.0.
Added note for npm commands for running the application against local APIs versus production. The correct npm command for running against production was found here https://github.com/bitwarden/web/issues/666.
Added more lines to the services.module.ts example to better reflect the actual file.
* Added CORS common issue and solution to README.md
* Changed Node.js version notes for real this time.
