Upstream/bitwarden-browser
1
0
Fork 0
mirror of https://github.com/bitwarden/browser.git synced 2024-12-20 16:07:45 +01:00
Code Issues Projects Releases Wiki Activity
6cea32839b
bitwarden-browser/apps/web/config/cloud.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

21 lines
634 B
JSON
Raw Normal View History

Set urls from config file (#1151) * 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
2021-08-25 20:15:31 +02:00
{
"urls": {
"icons": "https://icons.bitwarden.net",
EC-265 - SCIM configuration page in org admin (#3065) * EC-265 - Initial stubs for SCIM config UI * EC-265 - Scim config screen and plumbing * EC-265 - Scim config component works! Needs cleanup * EC-265 - Finalize scim config screen * EC-265 - Remove scim url from storage and env urls * EC-265 - Refactor to use new component library * EC-265 - Angular warnings on disabled attr resolved * EC-265 - Continued transition to new components * EC-265 - Page loading spinner pattern * EC-265 - final SCIM configuration form changes * scim cleanup * use scim urls * suggested changes * feedback fixes * remove return * Move scimUrl logic to EnvironmentService * Refactor scim url handling Co-authored-by: Kyle Spearrin <kyle.spearrin@gmail.com> Co-authored-by: Thomas Rittson <trittson@bitwarden.com>
2022-07-15 15:35:30 +02:00
"notifications": "https://notifications.bitwarden.com",
"scim": "https://scim.bitwarden.com"
Move WebConstants values to environment config files (#1184) * Moving the web constants to the app config for more flexibility * removing personal integrations from QA * changing the PayPal Configuration setup to match the pattern in the services module * removing the webConstants file after successful test * renaming the braintree config key to something more understandable
2021-09-09 23:18:46 +02:00
},
"stripeKey": "pk_live_bpN0P37nMxrMQkcaHXtAybJk",
"braintreeKey": "production_qfbsv8kc_njj2zjtyngtjmbjd",
"paypal": {
"businessId": "4ZDA7DLUUJGMN",
"buttonAction": "https://www.paypal.com/cgi-bin/webscr"
Update local web development instructions (#1208) * 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>
2021-10-22 14:50:08 +02:00
},
"dev": {
"proxyApi": "https://api.bitwarden.com",
"proxyIdentity": "https://identity.bitwarden.com",
[PM-3881] Fix ENV=cloud npm run build:oss:watch (#6262)
2023-09-12 15:10:08 +02:00
"proxyEvents": "https://events.bitwarden.com",
"proxyNotifications": "https://notifications.bitwarden.com"
[SG-439] Add feature flags to web (#3092) * Add feature flags to web * Remove extra file from dev
2022-07-13 18:22:58 +02:00
},
Remove showPasswordless conditionals (#11928) Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
2024-11-15 18:34:02 +01:00
"flags": {}
Set urls from config file (#1151) * 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
2021-08-25 20:15:31 +02:00
}
Reference in New Issue Copy Permalink