- commit
- 885c663bcd45f45941ff45a522c7cfe018dee4ec
- parent
- 2109b2c6b0c052bcad33d626f3b532fae09b9745
- author
- Dami <dami.etoile@gmail.com>
| D | deploy/ | 14 | -------------- |
| M | deploy/ | 14 | ++++++++++++++ |
| M | docs/ | 8 | ++++---- |
@@ -1,14 +0,0 @@
1-# Add to the relay host's Caddyfile. The edge machine reaches this listener2-# over the tailnet only; the port is not published anywhere else.3-http://012.run:8080, http://*.012.run:8080 {4- reverse_proxy 127.0.0.1:74475- @signerQR path /qr.svg /r/*/qr.svg6- log_skip @signerQR7- log {8- output file /logs/access.json {9- roll_size 10MiB10- roll_keep 711- }12- format json13- }14-}@@ -28,3 +28,17 @@ https://tiny.tailbe516a.ts.net {
2828 format json2929 }3030 }31+32+# Public domain via the Fly edge over the tailnet. Not published anywhere else.33+http://012.run:8080, http://*.012.run:8080 {34+ reverse_proxy 127.0.0.1:744735+ @signerQR path /qr.svg /r/*/qr.svg36+ log_skip @signerQR37+ log {38+ output file /logs/access.json {39+ roll_size 10MiB40+ roll_keep 741+ }42+ format json43+ }44+}@@ -14,7 +14,7 @@ fly certs check 012.run
1414 fly certs check "*.012.run"1515 ```1616 17-DNS at the registrar, all DNS-only records: A and AAAA for `012.run` and `*.012.run` pointing at the app's addresses from `fly ips list`, and a `_acme-challenge.012.run` CNAME from `fly certs setup "*.012.run"` for the wildcard certificate. The relay host's Caddyfile serves `012.run:8080` and `*.012.run:8080` over plain HTTP for the edge; see `deploy/edge/slate.Caddyfile.snippet`. After the certificates issue, set `--public-url https://012.run` on the relay so signed requests, NIP-11 and site hosts use the public name. The ts.net name stays tailnet only.17+DNS at the registrar, all DNS-only records with Cloudflare's Universal SSL turned off so its challenge records do not shadow Fly's: A and AAAA for `012.run` and `*.012.run` pointing at the app's addresses from `fly ips list`, and a `_acme-challenge.012.run` CNAME from `fly certs setup "*.012.run"` for the wildcard certificate. The relay host's Caddyfile, `deploy/tiny.Caddyfile`, serves `012.run:8080` and `*.012.run:8080` over plain HTTP for the edge. After the certificates issue, set `--public-url https://012.run` on the relay so signed requests, NIP-11 and site hosts use the public name. The ts.net name stays tailnet only.1818 1919 ## Repository hosting2020 @@ -22,13 +22,13 @@ The relay hosts Git repositories over GRASP. Use [ngit](https://ngit.dev) so the
2222 2323 ```sh2424 ngit account login25-ngit init --name tiny --identifier tinyrelay --grasp-server tiny.tailbe516a.ts.net \25+ngit init --name tiny --identifier tinyrelay --grasp-server 012.run \2626 --description "self-hosted, multitenant Nostr relay"27-git remote add tiny nostr://<owner npub>/tiny.tailbe516a.ts.net/tinyrelay27+git remote add tiny nostr://<owner npub>/012.run/tinyrelay2828 git push tiny main --tags2929 ```3030 31-Later pushes are plain `git push tiny`. Anyone can clone the repository with `git clone nostr://<owner npub>/tiny.tailbe516a.ts.net/tinyrelay`, or with plain Git from `https://tiny.tailbe516a.ts.net/<owner npub>/tinyrelay.git`.31+Later pushes are plain `git push tiny`. `ngit init` rewrites `origin` to the nostr address each time it runs; set it back to GitHub afterwards. Anyone can clone the repository with `git clone nostr://<owner npub>/012.run/tinyrelay`, or with plain Git from `https://012.run/<owner npub>/tinyrelay.git`.3232 3333 ## Web operations3434