[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [community/develop] Update colors in relay guide
commit 43c584877255c628207c5bf4f014c845df03030f
Author: hiro <hiro@xxxxxxxxxxxxxx>
Date: Thu Aug 29 15:17:14 2019 +0200
Update colors in relay guide
---
.../bridge/centos-rhel-opensuse/contents.lr | 14 ++++++++------
.../technical-setup/bridge/debian-ubuntu/contents.lr | 2 ++
.../technical-setup/bridge/docker/contents.lr | 2 ++
.../technical-setup/bridge/freebsd/contents.lr | 6 ++++--
.../technical-setup/bridge/getting-help/contents.lr | 2 ++
5 files changed, 18 insertions(+), 8 deletions(-)
diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
index 091dbb5..2d232a7 100644
--- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
@@ -1,10 +1,12 @@
_model: page
---
+color: primary
+---
title: CentOS / RHEL / OpenSUSE
---
body:
-### 1. Install tor and dependencies
+### 1. Install tor and dependencies
* Redhat / RHEL:
@@ -19,7 +21,7 @@ yum install git golang tor
zypper install tor go git
```
-### 2. Build obfs4proxy and move it into place.
+### 2. Build obfs4proxy and move it into place.
Heavily outdated versions of git can make `go get` fail, so try upgrading to a more recent git version if you're running into this problem.
@@ -71,7 +73,7 @@ ContactInfo <address@xxxxxxxxx>
Nickname PickANickname
```
- Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options.
+ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options.
* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.
@@ -83,7 +85,7 @@ Nickname PickANickname
To confirm your bridge is running with no issues, you should see something like this:
-```
+```
[notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>'
[notice] Your Tor bridge's hashed identity key fingerprint is '<NICKNAME> <HASHED FINGERPRINT>'
[notice] Registered server transport 'obfs4' at '[::]:46396'
@@ -91,7 +93,7 @@ To confirm your bridge is running with no issues, you should see something like
[notice] Bootstrapped 100%: Done
[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
-```
+```
### 6. Final notes
@@ -105,7 +107,7 @@ html: two-columns-page.html
---
key:
-2
+2
---
color: primary
---
diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
index d1eeb17..41b4f76 100644
--- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Debian / Ubuntu
---
body:
diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr
index 1c36012..f8925a1 100644
--- a/content/relay-operations/technical-setup/bridge/docker/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Docker
---
body:
diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
index d4bb28e..9088fa5 100644
--- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: FreeBSD
---
html: two-columns-page.html
@@ -47,7 +49,7 @@ Nickname PickANickname
Log notice file /var/log/tor/notices.log
```
-Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options.
+Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options.
* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.
@@ -67,7 +69,7 @@ sysrc tor_enable=YES
service tor start
```
-### 5. Monitor your logs
+### 5. Monitor your logs
To confirm your bridge is running with no issues, you should see something like this in `/var/log/tor/notices.log`:
diff --git a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr
index 828d351..cb72875 100644
--- a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Getting help
---
body:
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits