|
|
@@ -20,8 +20,8 @@ workshops.
|
|
20
|
20
|
One of these workshops, which happened on the morning of the last day, was about
|
|
21
|
21
|
installing [Synapse](https://github.com/matrix-org/synapse), the reference
|
|
22
|
22
|
Matrix homeserver implementation. The goal was to give attendees a presentation
|
|
23
|
|
-about what Matrix is, get them to install their own homeserver, and, if possible, to
|
|
24
|
|
-get everyone's server to federate with everyone else's.
|
|
|
23
|
+about what Matrix is, get them to install their own homeserver, and, if
|
|
|
24
|
+possible, to get everyone's server to federate with everyone else's.
|
|
25
|
25
|
|
|
26
|
26
|
This is not a trivial thing to do, especially when the technical expertise of
|
|
27
|
27
|
the attendence looks quite diverse. After a quick brainstorm on how to do that,
|
|
|
@@ -89,7 +89,9 @@ of the post.)
|
|
89
|
89
|
The workshop's host can then hand out the domain name attached to a server to
|
|
90
|
90
|
each attendee, who can then log in via SSH to the server and install and
|
|
91
|
91
|
configure a Matrix homeserver (including, if applicable, its built-in ACME
|
|
92
|
|
-support for automatic provisioning of the certificate needed for federation).
|
|
|
92
|
+support for automatic provisioning of the certificate needed for federation). As
|
|
|
93
|
+an example, [here](https://git.io/JelHi) are the instructions we got the
|
|
|
94
|
+attendees to follow during our workshop at Ubucon Europe.
|
|
93
|
95
|
|
|
94
|
96
|
|
|
95
|
97
|
*One of the domains I handed out during our workshop at Ubucon*
|
