Compare commits

..

No commits in common. "84473fb544bc7dd6f90d3532c275cf32e9ea7a67" and "3e30357cf204ef5c7fc19b70f292556d63d07f4a" have entirely different histories.

2 changed files with 3 additions and 15 deletions

View file

@ -96,18 +96,6 @@
width: fit-content;
}
.doll-quote figcaption {
font-size: 0.8em;
color: var(--dark2);
background-color: var(--middle1);
width: fit-content;
padding: 0 0.5ch;
}
.doll-quote figcaption + blockquote {
border-top: 2px solid var(--middle1);
}
.mermaid {
width: fit-content;
color: var(--middle1);

View file

@ -119,7 +119,7 @@ description: how it stores secrets alongside its code
age answers that question by letting doll use ed25519 keys to encrypt and decrypt doll's data.
[quote(important ^noe message):ed25519 would be a good name for a doll!!]
[quote:ed25519 would be a good name for a doll... ^n]
since we're deploying to machines with presumably an SSH server running, and presumably
the doll also has an SSH client, all of these ends have SSH keys we can use
@ -179,7 +179,7 @@ description: how it stores secrets alongside its code
# like `EDITOR="code -w"` will open a vscode tab.... (close tab to save)
]
this usually shows a nice default yaml file, move all that into the shadow realm.,
this usually shows a nice default yaml file, yeet all that into the garbage.
we wanna store something useful like... an authentication token to a certain doll's
multicelluar digital cortex.
@ -366,7 +366,7 @@ description: how it stores secrets alongside its code
&secrets........ but what about automation
that silly [code:.sops.yaml] third thing it mentioned huh? c:
that silly [code:.sops.yaml] thing huh, c:
why did we tag the age keys with [code:op_] and [code:m_]? so we can find them. in a script.