```
,-. ,-. ,-,-. . ,-. .    ,-. ,-. |- ,-. ,-. ,-| . ,-. |     ,-. |  ,-. . . ,-|
| | |-' | | | | | | | ,. |-' `-. |  |   ,-| | | | | | |  ,. |   |  | | | | | |
`-| `-' ' ' ' ' ' ' ' `' `-' `-' `' '   `-^ `-' ' `-' `' `' `-' `' `-' `-' `-'
 ,|
 `'
```

## how this capsule works

this capsule runs molly-brown.

the "server" is actually—at any given moment—one or more Pods in a kubernetes cluster. users have no shell access (not even admins). content is pulled dynamically from users' individual git repositories on startup / every 60 seconds. the server doesn't store anything beyond the lifetime of the Pod (modulo emptyDir implementation details), retains no state, and makes no attempt to do anything like "backups".

---

the content for the gemini DocBase is maintained at (contributions considered):
=> https://code.estradiol.cloud/tamsin/gemini.estradiol.cloud code.estradiol.cloud/tamsin/gemini.estradiol.cloud

container image and kubernetes configurations are at:
=> https://code.estradiol.cloud/tamsin/molly-brown-docker code.estradiol.cloud/tamsin/molly-brown-docker
=> https://gitlab.com/no_reply/sublingual/-/tree/trunk/estradiol.cloud/molly-brown [GitLab]: kubernetes config (flux-cd)