on master help sign in
Move Ledger instructions into usage section
commitff4345630d4e472829828b5712b157e743e47320 authorMorgan Sutherland <morgan@morgansutherland.com> dateThu 18 Apr 2019, 13:36 (8 years ago) parent61e5ee6
1 file changed+16−18
README.md+16−18
README.md+16−18
@@ -13,10 +13,23 @@ Python 3.7.2
13131. To use Bridge, [download a release](https://github.com/urbit/bridge/releases) and unzip it (`bridge-$version.zip`).
14142. Open up your command line interface (Terminal on MacOS, Command Prompt on Windows).
15153. `cd` into the `bridge-$version` directory.
16−4. Run this command: `python3 -m http.server 5000 --bind 127.0.0.1`
16+4. Run this command: `python3 -m http.server 5000 --bind 127.0.0.1`. If you're using Bridge with a Ledger hardware wallet, skip this step and see the Ledger Support subsection below.
17175. You can then use Bridge by navigating to http://localhost:5000 using a web browser.
1818
19−### Verify checksums
19+#### Ledger Support
20+
21+To authenticate and sign transactions with a [Ledger](https://www.ledger.com/), Bridge must be serving over HTTPS on localhost. This requires self-signed certificates. You can do this via the following:
22+
23+* Install [mkcert](https://github.com/FiloSottile/mkcert)
24+* If you're using Firefox, additionally install [nss](https://github.com/nss-dev/nss)
25+* Install a local certificate authority via `mkcert -install`
26+* In your `bridge` directory, generate a certificate valid for localhost via
27+ `mkcert localhost`. This will produce two files: `localhost.pem`, the local
28+ certificate, and `localhost-key.pem`, its corresponding private key.
29+* Run `python bridge-https.py`
30+* Navigate to https://localhost:4443 in a web browser
31+
32+### Verify Checksums
2033
2134To validate your downloaded file's integrity, compare the lines in checksum.txt to SHA-256 hashes of the `bridge-$version` directory's contents.
2235
@@ -31,7 +44,7 @@ To validate your downloaded file's integrity, compare the lines in checksum.txt
3144Clone the repo, and use a simple `npm install`. You can then use a `npm run
3245build` to create an optimised static build (serve it with e.g. [serve][serv]).
3346
34−### General notes
47+### General Notes
3548
3649For development, use `npm run pilot` to get going after a `npm install`. This
3750will boot up a Ganache node in the background, deploy the Azimuth contracts to
@@ -50,21 +63,6 @@ $ nvm use v11.0.0
5063
5164before running `npm run pilot`.
5265
53−### Ledger support
54−
55−To authenticate and sign transactions with a Ledger, Bridge must be serving
56−over HTTPS on localhost. This requires self-signed certificates. You can do
57−this via the following:
58−
59−* Install [mkcert](https://github.com/FiloSottile/mkcert)
60−* If you're using Firefox, additionally install [nss](https://github.com/nss-dev/nss)
61−* Install a local certificate authority via `mkcert -install`
62−* In your `bridge` directory, generate a certificate valid for localhost via
63− `mkcert localhost`. This will produce two files: `localhost.pem`, the local
64− certificate, and `localhost-key.pem`, its corresponding private key.
65−* Run `python bridge-https.py`
66−* Navigate to https://localhost:4443 in a web browser
67−
6866### Useful Accounts
6967
7068The ecliptic owner is the only account that's able to create galaxies, so