Latest code. Working voice, still needs some ui cleanup and accessibility fixes but in decent shape.

skald-install.md

@@ -58,7 +58,7 @@ chmod go-rw data/key.pem
 ```
 
 Since certificates are regularly rotated, this should be done in a monthly
-cron job (or a *SystemD* timer unit, if you're feeling particularly kinky).
+cron job or a systemd timer unit.
 
 ### Run Skald on the server
 
@@ -148,13 +148,13 @@ skaldctl -insecure create-hall -hall city-watch
 Create an "op", a user with hall moderation privileges:
 
 ```sh
-skaldctl create-user -hall city-watch -user vimes -permissions op
+skaldctl create-user -hall city-watch -user Username -permissions op
 ```
 
 Set the new user's password:
 
 ```sh
-skaldctl set-password -hall city-watch -user vimes
+skaldctl set-password -hall city-watch -user Username
 ```
 
 You should now be able to test your Skald installation by pointing a web
@@ -163,8 +163,8 @@ browser at <https://skald.example.org:8443/hall/city-watch/>.
 Create an ordinary user:
 
 ```sh
-skaldctl create-user -hall city-watch -user fred
-skaldctl set-password -hall city-watch -user fred
+skaldctl create-user -hall city-watch -user Participant
+skaldctl set-password -hall city-watch -user Participant
 ```
 
 Check the results:
@@ -177,6 +177,18 @@ skaldctl list-users -l -hall city-watch
 Type `skaldctl -help`, `skaldctl create-hall -help`, etc. for more
 information.
 
+### Recording dependency
+
+Skald recordings are single mixed Ogg Opus audio files.  Recording requires
+`ffmpeg` on the server:
+
+```sh
+ffmpeg -version
+```
+
+If `ffmpeg` is missing or cannot be started, Skald reports a recording error
+to the operator instead of creating a partial recording.
+
 ## Advanced configuration
 
 Skald is designed to be exposed directly to the Internet.  If your server
@@ -235,10 +247,21 @@ First, you might need to inform Skald of the URL at which users connect
 ```
 
 Second, and depending on your proxy implementation, you might need to
-request that the proxy pass WebSocket handshakes to the URL at `ws`; for
-example, with Nginx, you will need to say something like the following:
+proxy normal Skald paths such as `/hall/` and `/skald-api/`, and pass
+WebSocket handshakes to the URL at `ws`; for example, with Nginx, you will
+need to say something like the following:
 
 ```
+location /hall/ {
+    proxy_pass https://localhost:8443/hall/;
+    proxy_set_header Host $http_host;
+}
+
+location /skald-api/ {
+    proxy_pass https://localhost:8443/skald-api/;
+    proxy_set_header Host $http_host;
+}
+
 location /ws {
     proxy_pass https://localhost:8443/ws;
     proxy_set_header Upgrade $http_upgrade;