Adding Tahoe-LAFS (conclusion)

Added dependencies and instructions to spawn 4 servers for development
purposes.

Currently the servers have to be spawned manually every time they are
required, but #10 has some thoughts about how to automate this in the
future.

README.md

@@ -47,6 +47,37 @@ to discuss what you would like to change.
 
 ### Set up the developer environment
 
+Initiate Tahoe-LAFS servers (one introducer, two storage servers and a client server):
+
+Introducer server:
+
+```sh
+.venv/bin/tahoe create-introducer --listen=tcp --port=5555 --location=tcp:localhost:5555 ./introducer
+.venv/bin/tahoe -d introducer run &>/dev/null &
+```
+
+Two storage servers:
+
+```sh
+.venv/bin/tahoe create-node --introducer $(cat introducer/private/introducer.furl) --nickname storage0 --webport 6001 --location tcp:localhost:6003 --port 6003 ./storage0
+.venv/bin/tahoe create-node --introducer $(cat introducer/private/introducer.furl) --nickname storage1 --webport 6101 --location tcp:localhost:6103 --port 6103 ./storage1
+.venv/bin/tahoe -d storage0 run &>/dev/null &
+.venv/bin/tahoe -d storage1 run &>/dev/null &
+```
+
+Client:
+
+```sh
+.venv/bin/tahoe create-client --introducer $(cat introducer/private/introducer.furl) --nickname webapp --webport 6401 --shares-total=3 --shares-needed=2 --shares-happy=3 ./webapp
+.venv/bin/tahoe -d webapp run &>/dev/null &
+```
+
+The commands should return four PIDs. Note them down to kill them later, when finished, with:
+
+```sh
+kill -9 <PID>
+```
+
 ### Getting ready for your first pull request
 
 Please make sure to update tests as appropriate.