6e4782784c
* 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 |
||
|---|---|---|
| .github/workflows | ||
| config | ||
| jslib@66eec2b022 | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| config.js | ||
| CONTRIBUTING.md | ||
| crowdin.yml | ||
| dev-server.shared.pem | ||
| Dockerfile | ||
| entrypoint.sh | ||
| gulpfile.js | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE.txt | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.json | ||
| tslint.json | ||
| webfonts.list | ||
| webpack.config.js | ||
The Bitwarden web project is an Angular application that powers the web vault (https://vault.bitwarden.com/).
Build/Run
Requirements
- Node.js v8.11 or greater
Run the app
For local development, run the app with:
npm install
npm run build:watch
You can now access the web vault in your browser at https://localhost:8080.
If you want to point the development web vault to the production APIs, you can run using:
npm install
ENV=production npm run build:watch
You can also manually adjusting your API endpoint settings by adding config/development.js overriding any of the values in config/base.json. For example:
{
"proxyApi": "http://your-api-url",
"proxyIdentity": "http://your-identity-url",
"proxyEvents": "http://your-events-url",
"proxyNotifications": "http://your-notifications-url",
"proxyPortal": "http://your-portal-url",
"allowedHosts": ["hostnames-to-allow-in-webpack"]
}
To pick up the overrides in the newly created config/development.js file, run the app with:
npm run build:dev:watch
Contribute
Code contributions are welcome! Please commit any pull requests against the master branch. Learn more about how to contribute by reading the CONTRIBUTING.md file.
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.