commit 3f8d464855bafb64cc3f6918964f09423ba0014e · kot.pink/core

+41
docs/hacking.md
···

       32
       32
        
       nix run .#watch-tailwind

     

       33
       33
        
       ```

     

       34
       34
        
       

     

       35
       35
       +
       To authenticate with the appview, you will need redis and

     

       36
       36
       +
       OAUTH JWKs to be setup:

     

       37
       37
       +
       

     

       38
       38
       +
       ```

     

       39
       39
       +
       # oauth jwks should already be setup by the nix devshell:

     

       40
       40
       +
       echo $TANGLED_OAUTH_JWKS

     

       41
       41
       +
       {"crv":"P-256","d":"tELKHYH-Dko6qo4ozYcVPE1ah6LvXHFV2wpcWpi8ab4","kid":"1753352226","kty":"EC","x":"mRzYpLzAGq74kJez9UbgGfV040DxgsXpMbaVsdy8RZs","y":"azqqXzUYywMlLb2Uc5AVG18nuLXyPnXr4kI4T39eeIc"}

     

       42
       42
       +
       

     

       43
       43
       +
       # if not, you can set it up yourself:

     

       44
       44
       +
       go build -o genjwks.out ./cmd/genjwks

     

       45
       45
       +
       export TANGLED_OAUTH_JWKS="$(./genjwks.out)"

     

       46
       46
       +
       

     

       47
       47
       +
       # run redis in at a new shell to store oauth sessions

     

       48
       48
       +
       redis-server

     

       49
       49
       +
       ```

     

       50
       50
       +
       

     

       35
       51
        
       ## running a knot

     

       36
       52
        
       

     

       37
       53
        
       An end-to-end knot setup requires setting up a machine with

     
···

       71
       87
        
       git remote add local-dev git@nixos-shell:user/repo

     

       72
       88
        
       git push local-dev main

     

       73
       89
        
       ```

     

       90
       90
       +
       

     

       91
       91
       +
       ## running a spindle

     

       92
       92
       +
       

     

       93
       93
       +
       The above VM should already be running a spindle on

     

       94
       94
       +
       `localhost:6555`. You can head to the spindle dashboard on

     

       95
       95
       +
       `http://localhost:3000/spindles`, and register a spindle

     

       96
       96
       +
       with hostname `localhost:6555`. It should instantly be

     

       97
       97
       +
       verified. You can then configure each repository to use this

     

       98
       98
       +
       spindle and run CI jobs.

     

       99
       99
       +
       

     

       100
       100
       +
       Of interest when debugging spindles:

     

       101
       101
       +
       

     

       102
       102
       +
       ```

     

       103
       103
       +
       # service logs from journald:

     

       104
       104
       +
       journalctl -xeu spindle

     

       105
       105
       +
       

     

       106
       106
       +
       # CI job logs from disk:

     

       107
       107
       +
       ls /var/log/spindle

     

       108
       108
       +
       

     

       109
       109
       +
       # debugging spindle db:

     

       110
       110
       +
       sqlite3 /var/lib/spindle/spindle.db

     

       111
       111
       +
       

     

       112
       112
       +
       # litecli has a nicer REPL interface:

     

       113
       113
       +
       litecli /var/lib/spindle/spindle.db

     

       114
       114
       +
       ```