From 61275dd3e5caa17b9ccae5da506df0a61f0ffc22 Mon Sep 17 00:00:00 2001 From: Alec Date: Tue, 27 Jun 2023 10:56:41 -0400 Subject: [PATCH] Update README.md --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9bba9fb..7b6eede 100644 --- a/README.md +++ b/README.md @@ -58,8 +58,11 @@ The entrypoint for the application is `index.js` at the root. Before starting the Node.js server, you'll need a Redis server running locally on the default port. This is what's used to store active games and keep any number of Node.js servers in sync. I followed this tutorial, specifically using the installation method that uses -Windows Subsystem for Linux (WSL), since I am on a windows machine. Once I got WSL and Redis installed and was in a linux environment -running in the powershell, I tested out the Redis server by using the Redis CLI +Windows Subsystem for Linux (WSL), since I am on a windows machine. In a powershell, I simply run `wsl` and then `redis-server`, at which point you should see something like the following startup logs. + +![image](https://github.com/AlecM33/Werewolf/assets/24642328/206dd89c-6a48-4c49-9bb5-aeac829bc26d) + +I tested out the Redis server by using the Redis CLI (see their getting started page). Once that's done, if you haven't already, install Node.js. This should include the node package