You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: other/bootstrap_daemon/README.md
+128-9Lines changed: 128 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,29 @@
1
1
#Instructions
2
2
3
3
-[For `systemd` users](#systemd)
4
+
-[Setting up](#systemd-setting-up)
5
+
-[Updating](#systemd-updating)
4
6
-[Troubleshooting](#systemd-troubleshooting)
5
7
<br>
6
-
-[For `init.d` users](#initd)
7
-
-[Troubleshooting](#initd-troubleshooting)
8
+
-[For `SysVinit` users](#sysvinit)
9
+
-[Setting up](#sysvinit-setting-up)
10
+
-[Updating](#sysvinit-updating)
11
+
-[Troubleshooting](#sysvinit-troubleshooting)
12
+
<br>
13
+
-[For `Docker` users](#docker)
14
+
-[Setting up](#docker-setting-up)
15
+
-[Updating](#docker-updating)
16
+
-[Troubleshooting](#docker-troubleshooting)
8
17
9
18
10
-
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.
19
+
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.
11
20
12
21
13
22
<aname="systemd" />
14
-
##For `systemd` users:
23
+
##For `systemd` users
24
+
25
+
<aname="systemd-setting-up" />
26
+
###Setting up
15
27
16
28
For security reasons we run the daemon under its own user.
17
29
@@ -56,8 +68,31 @@ Get your public key and check that the daemon initialized correctly:
56
68
sudo grep "tox-bootstrapd" /var/log/syslog
57
69
```
58
70
71
+
<aname="systemd-updating" />
72
+
###Updating
73
+
74
+
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.
75
+
76
+
To update the daemon first stop it:
77
+
78
+
```sh
79
+
sudo systemctl stop tox-bootstrapd.service
80
+
```
81
+
82
+
Then update your toxcore git repository, rebuild the toxcore and the daemon and make sure to install them.
83
+
84
+
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.
85
+
86
+
After all of this is done, simply start the daemon back again:
- Make sure tox-bootstrapd location matches its path in tox-bootstrapd.service file.
81
116
82
117
83
-
<aname="initd" />
84
-
##For `init.d` users
118
+
<aname="sysvinit" />
119
+
##For `SysVinit` users
120
+
121
+
<aname="sysvinit-setting-up" />
122
+
###Setting up
85
123
86
124
For security reasons we run the daemon under its own user.
87
125
@@ -126,8 +164,29 @@ Get your public key and check that the daemon initialized correctly:
126
164
sudo grep "tox-bootstrapd" /var/log/syslog
127
165
```
128
166
129
-
<aname="initd-troubleshooting" />
130
-
###Troubleshooting:
167
+
<aname="sysvinit-updating" />
168
+
###Updating
169
+
170
+
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.
171
+
172
+
To update the daemon first stop it:
173
+
174
+
```sh
175
+
sudo service tox-bootstrapd stop
176
+
```
177
+
178
+
Then update your toxcore git repository, rebuild the toxcore and the daemon and make sure to install them.
179
+
180
+
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.
181
+
182
+
After all of this is done, simply start the daemon back again:
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.
228
+
229
+
You can check logs for your public key or any errors:
230
+
```sh
231
+
sudo docker logs tox-bootstrapd
232
+
```
233
+
234
+
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.
235
+
236
+
<aname="docker-updating" />
237
+
###Updating
238
+
239
+
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.
240
+
241
+
To update the daemon, all you need is to erase current container with its image:
0 commit comments