From 478692dfc1752ee178d7ef18b09c53861803bf0b Mon Sep 17 00:00:00 2001
From: psvenk <45520974+psvenk@users.noreply.github.com>
Date: Tue, 2 Apr 2019 16:33:56 -0400
Subject: [PATCH] Update hosting instructions

I forgot to mention that people should run `npm install`. I have now added it.
---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c96b877c..87150fc6 100644
--- a/README.md
+++ b/README.md
@@ -40,7 +40,8 @@ If you would like to directly contribute to Aspine, you can fork this repository
   * On Windows or macOS, download node.js and redis from their websites, and install them.
   * On GNU+Linux, you should be able to find these in your package manager (e.g. `apt`/`dpkg`, `yum`/`dnf`, `zypper`, `pacman`). npm may be in a separate package from node.js.
 * Open a terminal or command prompt, navigate to the directory in which you cloned the Aspine git repository, and run `redis-server redis.conf`.
-* Open another terminal or command prompt, navigate to that same directory, and run `node ./serve.js insecure`, or `node ./serve.js insecure fake` to use the `sample.json` file instead of pulling from Aspen (for faster testing).
+* Open another terminal or command prompt, navigate to that same directory, and run `npm install` to install the required dependencies.
+* In the same terminal or command prompt, run `node ./serve.js insecure`, or `node ./serve.js insecure fake` to use the `sample.json` file instead of pulling from Aspen (for faster testing).
 
 These instructions have only been tested on GNU+Linux. You might need to change your `PATH` on Windows if you get an error saying that `node` is not found after installing node.js.