stack-orchestrator/stack_orchestrator/data/stacks/kubo
A. F. Dudley 5a1399f2b2
Some checks failed
Lint Checks / Run linter (push) Successful in 14s
K8s Deployment Control Test / Run deployment control suite on kind/k8s (push) Failing after 31s
Database Test / Run database hosting test on kind/k8s (push) Failing after 31s
Container Registry Test / Run contaier registry hosting test on kind/k8s (push) Failing after 36s
Apply pre-commit linting fixes
Fix trailing whitespace and end-of-file issues across codebase.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-20 23:16:44 -05:00
..
README.md Rename app -> stack_orchestrator (#625) 2023-11-07 00:06:55 -07:00
stack.yml Apply pre-commit linting fixes 2026-01-20 23:16:44 -05:00

Kubo (IPFS)

The Kubo stack currently uses the native IPFS docker image, therefore a single command will do:

laconic-so --stack kubo deploy up

If running locally, visit: http://localhost:5001/webui and explore the functionality of the WebUI.

If running in the cloud, visit IP:5001/webui and you'll likely see this error: "Could not connect to the IPFS API". To fix it:

  1. Get the container name with docker ps:

  2. Go into the container:

laconic-so --stack kubo deploy exec ipfs sh
  1. Enable CORS as described in point 2 of the error message. Copy/paste/run each line in sequence, then run exit to exit the container.

  2. Restart the container:

laconic-so --stack kubo deploy down
laconic-so --stack kubo deploy up
  1. Refresh the IP:5001/webui URL in your browser, you should now be connected to IPFS.