1 files changed, 128 insertions, 9 deletions

diff --git a/other/bootstrap_daemon/README.md b/other/bootstrap_daemon/README.md
index e77e3ae0..93e390ef 100644
--- a/other/bootstrap_daemon/README.md
+++ b/other/bootstrap_daemon/README.md
@@ -1,17 +1,29 @@
 #Instructions
 
 - [For `systemd` users](#systemd)
+  - [Setting up](#systemd-setting-up)
+  - [Updating](#systemd-updating)
   - [Troubleshooting](#systemd-troubleshooting)
 <br>
-- [For `init.d` users](#initd)
-  - [Troubleshooting](#initd-troubleshooting)
+- [For `SysVinit` users](#sysvinit)
+  - [Setting up](#sysvinit-setting-up)
+  - [Updating](#sysvinit-updating)
+  - [Troubleshooting](#sysvinit-troubleshooting)
+<br>
+- [For `Docker` users](#docker)
+  - [Setting up](#docker-setting-up)
+  - [Updating](#docker-updating)
+  - [Troubleshooting](#docker-troubleshooting)
 
 
-These instructions are primarily tested on Debian Linux, Wheezy for init.d and Jessie for systemd, but they should work on other POSIX-compliant systems too.
+These instructions are primarily tested on Debian Linux, Wheezy for SysVinit and Jessie for systemd, but they should work on other POSIX-compliant systems too.
 
 
 <a name="systemd" />
-##For `systemd` users:
+##For `systemd` users
+
+<a name="systemd-setting-up" />
+###Setting up
 
 For security reasons we run the daemon under its own user.
 
@@ -56,8 +68,31 @@ Get your public key and check that the daemon initialized correctly:
 sudo grep "tox-bootstrapd" /var/log/syslog
 ```
 
+<a name="systemd-updating" />
+###Updating
+
+You want to make sure that the daemon uses the newest toxcore, as there might have been some changes done to the DHT, so it's advised to update the daemon at least once every month.
+
+To update the daemon first stop it:
+
+```sh
+sudo systemctl stop tox-bootstrapd.service
+```
+
+Then update your toxcore git repository, rebuild the toxcore and the daemon and make sure to install them.
+
+Check if `tox-bootstrapd.service` in toxcore git repository was modified since the last time you copied it, as you might need to update it too.
+
+After all of this is done, simply start the daemon back again:
+
+```sh
+sudo systemctl start tox-bootstrapd.service
+```
+
+Note that `tox-bootstrapd.service` file might
+
 <a name="systemd-troubleshooting" />
-###Troubleshooting:
+###Troubleshooting
 
 - Check daemon's status:
 ```sh
@@ -80,8 +115,11 @@ sudo journalctl -f _SYSTEMD_UNIT=tox-bootstrapd.service
 - Make sure tox-bootstrapd location matches its path in tox-bootstrapd.service file.
 
 
-<a name="initd" />
-##For `init.d` users
+<a name="sysvinit" />
+##For `SysVinit` users
+
+<a name="sysvinit-setting-up" />
+###Setting up
 
 For security reasons we run the daemon under its own user.
 
@@ -126,8 +164,29 @@ Get your public key and check that the daemon initialized correctly:
 sudo grep "tox-bootstrapd" /var/log/syslog
 ```
 
-<a name="initd-troubleshooting" />
-###Troubleshooting:
+<a name="sysvinit-updating" />
+###Updating
+
+You want to make sure that the daemon uses the newest toxcore, as there might have been some changes done to the DHT, so it's advised to update the daemon at least once every month.
+
+To update the daemon first stop it:
+
+```sh
+sudo service tox-bootstrapd stop
+```
+
+Then update your toxcore git repository, rebuild the toxcore and the daemon and make sure to install them.
+
+Check if `tox-bootstrapd.sh` in toxcore git repository was modified since the last time you copied it, as you might need to update it too.
+
+After all of this is done, simply start the daemon back again:
+
+```sh
+sudo service tox-bootstrapd start
+```
+
+<a name="sysvinit-troubleshooting" />
+###Troubleshooting
 
 - Check daemon's status:
 ```sh
@@ -146,3 +205,63 @@ sudo grep "tox-bootstrapd" /var/log/syslog
 - Make sure tox-bootstrapd has read permission for the config file.
 
 - Make sure tox-bootstrapd location matches its path in the `/etc/init.d/tox-bootstrapd` init script.
+
+
+<a name="docker" />
+##For `Docker` users:
+
+<a name="docker-setting-up" />
+###Setting up
+
+If you are familiar with Docker and would rather run the daemon in a Docker container, run the following from this directory:
+
+```sh
+sudo docker build -t tox-bootstrapd docker/
+
+sudo useradd --home-dir /var/lib/tox-bootstrapd --create-home --system --shell /sbin/nologin --comment "Account to run Tox's DHT bootstrap daemon" --user-group tox-bootstrapd
+sudo chmod 700 /var/lib/tox-bootstrapd
+
+sudo docker run -d --name tox-bootstrapd --restart always -v /var/lib/tox-bootstrapd/:/var/lib/tox-bootstrapd/ -p 443:443 -p 3389:3389 -p 33445:33445 -p 33445:33445/udp tox-bootstrapd
+```
+
+We create a new user and protect its home directory in order to mount it in the Docker image, so that the kyepair the daemon uses would be stored on the host system, which makes it less likely that you would loose the keypair while playing with or updating the Docker container.
+
+You can check logs for your public key or any errors:
+```sh
+sudo docker logs tox-bootstrapd
+```
+
+Note that the Docker container runs a script which pulls a list of bootstrap nodes off https://nodes.tox.chat/ and adds them in the config file.
+
+<a name="docker-updating" />
+###Updating
+
+You want to make sure that the daemon uses the newest toxcore, as there might have been some changes done to the DHT, so it's advised to update the daemon at least once every month.
+
+To update the daemon, all you need is to erase current container with its image:
+
+```sh
+sudo docker stop tox-bootstrapd
+sudo docker rm tox-bootstrapd
+sudo docker rmi tox-bootstrapd
+```
+
+Then rebuild and run the image again:
+
+```sh
+sudo docker build -t tox-bootstrapd docker/
+sudo docker run -d --name tox-bootstrapd --restart always -v /var/lib/tox-bootstrapd/:/var/lib/tox-bootstrapd/ -p 443:443 -p 3389:3389 -p 33445:33445 -p 33445:33445/udp tox-bootstrapd
+```
+
+<a name="docker-troubleshooting" />
+###Troubleshooting
+
+- Check if the container is running:
+```sh
+sudo docker ps -a
+```
+
+- Check the log for errors:
+```sh
+sudo docker logs tox-bootstrapd
+```