Browse Source

readme updates

pull/60/head
Kyle Spearrin 9 years ago
parent
commit
41fb290666
  1. 2
      CONTRIBUTING.md
  2. 8
      README.md

2
CONTRIBUTING.md

@ -19,5 +19,7 @@ when creating your pull request: @@ -19,5 +19,7 @@ when creating your pull request:
5. Test your translations to make sure they look correct in the extension. Sometimes the UI can break due to translations
taking up more space than the original UI was built for. If possible, use a shorter or abbreviated version of the
word/sentence to accomedate the available space.
6. Be sure to watch for [future changes](https://github.com/bitwarden/browser/commits/master/src/_locales/en/messages.json)
to the `/src/_locales/en/messages.json` file so that your translation will stay up to date.
You can find an example of a proper translation pull request here: <https://github.com/bitwarden/browser/pull/49/files>

8
README.md

@ -13,11 +13,13 @@ The bitwarden browser extension is written using the Chrome Web Extension API an @@ -13,11 +13,13 @@ The bitwarden browser extension is written using the Chrome Web Extension API an
**Requirements**
- Node.js
- Gulp
- [Node.js](https://nodejs.org/en/)
- [Gulp](http://gulpjs.com/) (`npm install --global gulp-cli`)
- Chrome (preferred), Opera, or Firefox browser
By default the extension is targeting the production API. If you are running the [Core](https://github.com/bitwarden/core) API locally, you'll need to switch the extension to target your local API. Open `src/services/apiService.js` and set `this.baseUrl` to your local API instance (ex. `http://localhost:4000`).
By default the extension is targeting the production API. If you are running the [Core](https://github.com/bitwarden/core) API locally,
you'll need to switch the extension to target your local API. Open `src/services/apiService.js` and set `this.baseUrl` to your local
API instance (ex. `http://localhost:4000`).
Then run the following commands:

Loading…
Cancel
Save