forked from
tangled.org/core
Mirror of @tangled.org/core. Running on a Raspberry Pi Zero 2 (Please be gentle).
docs: add redis and spindle setup details
Signed-off-by: oppiliappan <me@oppi.li>
+41
+41
docs/hacking.md
+41
docs/hacking.md
···
32
32
nix run .#watch-tailwind
33
33
```
34
34
35
+
To authenticate with the appview, you will need redis and
36
+
OAUTH JWKs to be setup:
37
+
38
+
```
39
+
# oauth jwks should already be setup by the nix devshell:
40
+
echo $TANGLED_OAUTH_JWKS
41
+
{"crv":"P-256","d":"tELKHYH-Dko6qo4ozYcVPE1ah6LvXHFV2wpcWpi8ab4","kid":"1753352226","kty":"EC","x":"mRzYpLzAGq74kJez9UbgGfV040DxgsXpMbaVsdy8RZs","y":"azqqXzUYywMlLb2Uc5AVG18nuLXyPnXr4kI4T39eeIc"}
42
+
43
+
# if not, you can set it up yourself:
44
+
go build -o genjwks.out ./cmd/genjwks
45
+
export TANGLED_OAUTH_JWKS="$(./genjwks.out)"
46
+
47
+
# run redis in at a new shell to store oauth sessions
48
+
redis-server
49
+
```
50
+
35
51
## running a knot
36
52
37
53
An end-to-end knot setup requires setting up a machine with
···
86
70
```bash
87
71
git remote add local-dev git@nixos-shell:user/repo
88
72
git push local-dev main
73
+
```
74
+
75
+
## running a spindle
76
+
77
+
The above VM should already be running a spindle on
78
+
`localhost:6555`. You can head to the spindle dashboard on
79
+
`http://localhost:3000/spindles`, and register a spindle
80
+
with hostname `localhost:6555`. It should instantly be
81
+
verified. You can then configure each repository to use this
82
+
spindle and run CI jobs.
83
+
84
+
Of interest when debugging spindles:
85
+
86
+
```
87
+
# service logs from journald:
88
+
journalctl -xeu spindle
89
+
90
+
# CI job logs from disk:
91
+
ls /var/log/spindle
92
+
93
+
# debugging spindle db:
94
+
sqlite3 /var/lib/spindle/spindle.db
95
+
96
+
# litecli has a nicer REPL interface:
97
+
litecli /var/lib/spindle/spindle.db
89
98
```