anchor.diff:  use cargo's `-f` flag to force install `emerald-cli` and copy that version to the
   project directory.
   
  -##### Geth
  -If geth isn't available in your project directory, upon launching the app, it automatically
  -be downloaded and placed in your project base dir.
   
  -
  -### Run for development
  -
  -Firstly: a couple things aren't working right. If you can fix either of these issues,
  -@whilei will buy you a beer.
  -
  -- _Issue 1_: `webpack-dev-server` isn't working right with the current babel-webpack-electron-izing
  -  setup. So you've got to do your development in Electron for now. Which means you can't run `npm run start:web`. Bummer.
  -
  -With these caveats in mind, __you can run__:
  +=== Run for development
   
   _Terminal 1_
   ```shell
  -# This will begin a live-watching compiler for ./src/ and ./electron/ folders
  += This will begin a live-watching compiler for ./src/ and ./electron/ folders
   $ yarn build:all:dev
   ```
   
   _Terminal 2_
   ```shell
  -# This will begin the simulated electron app pulling from those compiled sources.
  += This will begin the simulated electron app pulling from those compiled sources.
   $ yarn start:electron
   ```
   
  -### Logs
  +=== Logs
   
  -#### Emerald logs
   Electron and Emerald logs persisted in:
   
    * OSX: `~/Library/Logs/EmeraldWallet/log.log`
    * Linux: `~/.config/EmeraldWallet/log.log`
   
  -
  -#### Geth logs
  -During development, you'll find geth's logs in `./logs` right in the project base directory.
  -
  -In production, logs will be nestled in
  -
  - * OSX: `~/Library/Application Support/EmeraldWallet/`
  - * Windows: `%USERPROFILE%\AppData\Roaming\EmeraldWallet\logs`
  -
  -### Building alternatively
  +=== Building alternatively
   
   You can also use a variety of alternate build options, eg.
   
  
positive.code: Emerald - Ethereum and Ethereum Classic Wallet
  ==============================================
  
  :rootdir: .
  :imagesdir: {rootdir}/images
  :toclevels: 2
  :toc:
  
  ifdef::env-github,env-browser[:badges:]
  ifdef::env-github,env-browser[:outfilesuffix: .adoc]
  
  ifdef::badges[]
  image:https://circleci.com/gh/ETCDEVTeam/emerald-wallet.svg?style=svg["CircleCI", link="https://circleci.com/gh/ETCDEVTeam/emerald-wallet"]
  image:https://badges.gitter.im/ethereumproject/emerald-wallet.svg[link="https://gitter.im/ethereumproject/emerald-wallet?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge"]
  image:https://travis-ci.org/ETCDEVTeam/emerald-wallet.png?branch=master[Travis CI Build Status, link=https://travis-ci.org/ETCDEVTeam/emerald-wallet]
  image:https://img.shields.io/github/license/ETCDEVTeam/emerald-wallet.svg?maxAge=2592000["License", link="https://github.com/ETCDEVTeam/emerald-wallet/blob/master/LICENSE"]
  image:https://ci.appveyor.com/api/projects/status/5u1j94oml44whqx6?svg=true[AppVeyor Build Status, link=https://ci.appveyor.com/project/etcdevteam/emerald-wallet/]
  image:https://codecov.io/gh/ETCDEVTeam/emerald-wallet/branch/master/graph/badge.svg[Codecov, link=https://codecov.io/gh/ETCDEVTeam/emerald-wallet]
  endif::[]
  
  
  ## Development instructions
  The recommended way to assert that you are using the correct version of node is to use https://github.com/nodenv/nodenv[nodenv], which will shim the `node` and `npm` commands and assert that the `local` version is set to what is specified in https://github.com/ETCDEVTeam/emerald-wallet/blob/master/.node-version[.node-version].
  
  Once nodenv is installed:
  
  
negative.code: $ npm run build:web
  ```
  
  === Building distributions in development
  You can run a distribution build in your development environment. Assuming
  you've already compiled `./src/` and `./electron/`, you'll be able to run:
  
  