cli.sgit.ai / Research / Running a vault locally
Running a vault locally
The question. "Just clone a vault and run it from there." Can sgit run a working vault, the web UI and the API, on a laptop, with no TLS to set up and no server to write?
Where it stands
| Status | Where it is said | |
|---|---|---|
| The vault server's API, inventoried; when TLS is and is not needed | research, 12 October | Running a vault locally |
Run the SG/Send container image rather than re-implement the server; Docker, Podman and Apple's container | decided 12 October; phase 1 built | Container first |
sgit serve and its subcommands (install, runtimes, status, logs, push, pull, stop, update) | shipped; in the 0.23.0 reference | sgit serve |
| Self-hosting a server for agents in VMs, containers and the cloud | documented | Self-hosting for agents |
The research documents, newest first
decision
sgit serve: container first. Options map and spike results
The decision to run the SG/Send container image rather than re-implement the server: the runtimes supported (including Apple's container and Podman), the spike results, and phase 1 as built.
researchsgit serve: running a vault locally — research and plan
How to run a vault locally: the vault server's API inventory, the browser modes, when TLS is and is not needed, and how much plumbing sgit would need.
This page as markdown · its source, admin/content/research/topics/serve.md