on master help sign in
Fix cd order
commit44a4c4a532cea681e640e1822a4a8e2ac5a611fc authorMorgan Sutherland <msutherl@users.noreply.github.com> dateThu 18 Apr 2019, 15:56 (8 years ago) parent8c56cd4
1 file changed+4−6
README.md+4−6
README.md+4−6
@@ -22,7 +22,7 @@ To use Bridge:
2222If you plan to authenticate and sign transactions with a Master Ticket, BIP39 mnemonic, Ethereum private key, or keystore file:
2323
24241. `cd` into the `bridge-$version` directory
25−2. Run this command: `python3 -m http.server 5000 --bind 127.0.0.1`
25+2. Run `python3 -m http.server 5000 --bind 127.0.0.1`
26263. Navigate to http://localhost:5000 using a web browser to access Bridge
2727
2828#### Running Bridge with Ledger support
@@ -32,11 +32,9 @@ If you plan to authenticate and sign transactions with a [Ledger](https://www.le
32321. Install [mkcert](https://github.com/FiloSottile/mkcert)
33332. If you're using Firefox, additionally install [nss](https://github.com/nss-dev/nss)
34343. Install a local certificate authority via `mkcert -install`
35−4. In the `bridge-$version` directory, generate a certificate valid for localhost via
36− `mkcert localhost`. This will produce two files: `localhost.pem`, the local
37− certificate, and `localhost-key.pem`, its corresponding private key
38−5. `cd` into the `bridge-$version` directory
39−6. Run `python bridge-https.py` from the `bridge-$version` directory
35+4. `cd` into the `bridge-$version` directory
36+5. Run `mkcert localhost` to generate a certificate valid for localhost. This will produce two files: `localhost.pem`, the local certificate, and `localhost-key.pem`, its corresponding private key
37+6. Run `python bridge-https.py`
40387. Navigate to https://localhost:4443 in a web browser to access Bridge
4139
4240### Verify checksums