Change Details

We have a step in the `dev_instructions` where the developer is supposed to run: ``` yarn babel-build yarn rsync yarn script dist/scripts/create-db.js ``` in the `keyserver` directory. However, unlike when we run `yarn dev` in `keyserver`, we don't source `node` from `nvm`. That means that if the developer has an incompatible version of `node` installed, running `yarn script dist/scripts/create-db.js` will fail. (In the future this sort of thing will be handled by `nix`)

We have a step in the `dev_instructions` where the developer is supposed to run: ``` yarn babel-build yarn rsync yarn script dist/scripts/create-db.js ``` in the `keyserver` directory. However, unlike when we run `yarn dev` in `keyserver`, we don't source `node` from `nvm`. That means that if the developer has an incompatible version of `node` installed, running `yarn script dist/scripts/create-db.js` may fail. (In the future this sort of thing will be handled by `nix`)

We have a step in the `dev_instructions` where the developer is supposed to run: ``` yarn babel-build yarn rsync yarn script dist/scripts/create-db.js ``` in the `keyserver` directory. However, unlike when we run `yarn dev` in `keyserver`, we don't source `node` from `nvm`. That means that if the developer has an incompatible version of `node` installed, running `yarn script dist/scripts/create-db.js` willmay fail. (In the future this sort of thing will be handled by `nix`)