ack/kokkoja-rel
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Character codes in typed text; the site and relay at app.kokkoja.com

Browse Source 
With the Text tool, Klammertext's codes give letters a keyboard lacks:
^o" is ö, ^s^ ß, ^a1 ā, ^130ED^ a code point of 4 to 6 digits,
^9053 53EF^ a sequence, ^^ a caret, replaced as each code is completed.
The public site and relay moved to app.kokkoja.com; the old name
redirects.  The Markdown documentation is withdrawn from the release
while it is converted to Klammertext; the README's links to it are
stale until then.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
ackandClaude Fable 5.1 committed 2026-10-13 20:40:09 +02:00
1 parent 34ca33d365
commit 89b4a41b2a
15 files changed
+364 -1273
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

deploy/README.md
+13 -10
View File
@@ -4,7 +4,8 @@ A Kokkoja *server* is one machine that does two things for a group of
users: it runs the relay, which passes the participants' encrypted
messages, and it serves the client as a web site, so that a guest can
join by opening a link with nothing installed. Neither stores anything.
The first one is Andy's VPS at `kokkoja.andykopra.com`.
The first one is Andy's VPS, reached at `app.kokkoja.com` (the older
name `kokkoja.andykopra.com` still works, redirected there).
| On the server | What it is |
|----------------------------|-------------------------------------------------|
@@ -15,10 +16,10 @@ The first one is Andy's VPS at `kokkoja.andykopra.com`.
| nginx site `kokkoja` | `https://<site>/` serves the client; `wss://<site>/relay` reaches the relay |
The client's `config.json` on the site says
`{"relay": "wss://kokkoja.andykopra.com/relay", "storage": "browser",
"site": "https://kokkoja.andykopra.com/"}`: the notebooks of anyone using
`{"relay": "wss://app.kokkoja.com/relay", "storage": "browser",
"site": "https://app.kokkoja.com/"}`: the notebooks of anyone using
the site are kept in their browser. A host with the local program uses
the server with `python3 kokkoja.py --relay wss://kokkoja.andykopra.com/relay`;
the server with `python3 kokkoja.py --relay wss://app.kokkoja.com/relay`;
the invitation is then a link to the site.
## Setting up or updating
@@ -38,14 +39,16 @@ denied (publickey)".
Steps a person does, once:
1. DNS: an A record `kokkoja.andykopra.com` pointing at the VPS
(82.221.141.89), in cPanel's Zone Editor, since andykopra.com is on
the orangewebsite.com nameservers. Check with
`host kokkoja.andykopra.com buffy.ns.orangewebsite.com`.
1. DNS: an A record `app.kokkoja.com` pointing at the VPS
(82.221.141.89), wherever kokkoja.com's DNS is managed (its registrar,
or the orangewebsite.com nameservers if delegated there). The older
name `kokkoja.andykopra.com` keeps its A record in cPanel's Zone
Editor and is redirected to app.kokkoja.com by nginx. Check with
`host app.kokkoja.com`.
2. TLS, after the name resolves and `deploy.sh` has run once:
ssh root@vps313847.iceservers.net certbot --nginx -d kokkoja.andykopra.com
ssh root@vps313847.iceservers.net certbot --nginx -d app.kokkoja.com -d kokkoja.andykopra.com
certbot adds the TLS listener to the nginx site and turns the plain
HTTP block into a redirect. Afterwards `setup_vps.sh` leaves the
@@ -57,7 +60,7 @@ Steps a person does, once:
vps-sentinel --accept
Checks: `https://kokkoja.andykopra.com/config.json` shows the
Checks: `https://app.kokkoja.com/config.json` shows the
configuration above; `systemctl status kokkoja-relay` is active;
`journalctl -u kokkoja-relay -n 20` shows it listening.