Zashiki Warashi

Compose and database peek

Zashiki Warashi finds Compose files in a project, lists DB-like services, and helps you copy a connection URI or open Compass — glue on top of Docker Desktop or OrbStack.

Local apps often ship with a docker-compose.yml (or compose.yaml) that only exists to run Postgres, MySQL, Redis, or Mongo. You do not want a second career as a Docker Desktop power user just to copy a connection string.

Zashiki Warashi peeks that stack from the project you already cataloged.

What “peek” means

For a selected project, the app:

  1. Discovers Compose files (project root and common nested locations)
  2. Lists DB-like services and whether they look running (docker compose ps via a cached docker binary)
  3. Surfaces host / port / user / database derived from compose and env
  4. Lets you copy a URI or open MongoDB Compass when the service is mongo
  5. Offers Up / Stop for those DB-oriented services — not a full substitute for docker compose day-to-day ops

This is observation + glue, not a Compose YAML editor, not volume browsers, not remote Docker fleets. For that class of tool, see vs Portainer.

Engine underneath

You still need Docker Desktop or OrbStack (or another engine that speaks docker compose). Zashiki does not ship a container runtime. Comparisons that stay honest:

Secrets stay out of the catalog DB

Connection URIs may include passwords from env files. Product rule: derive at runtime, do not persist passwords in SQLite, mask in the UI. Peek again when files change.

How this fits the Monday workflow

  1. Catalog the repo (start/stop)
  2. Start the app process if needed
  3. Up the DB services from the Stack pane
  4. Copy URI into your .env consumer — or open Compass for mongo
  5. If host ports collide with another project, use port reconciliation

Nested compose

Real repos bury compose under docker/ or infra/. Discovery walks a shallow depth and nested compose -f works for the log and stack paths the app supports. Exotic multi-file matrices may still need Terminal — the goal is the common path, not every Compose feature.

What we are not building (on purpose)

  • No Mongo / SQL query editor inside Zashiki
  • No DB provisioning from scratch in v1
  • No inventing a Docker GUI

Download: Releases. MIT.

FAQ

Does this replace Portainer or Docker Desktop?

No. It peeks and drives compose for DB-like services as part of a project house. Full container management stays with your engine UI.

Are database passwords stored in SQLite?

No. URIs are derived at runtime from compose/env. Passwords are not persisted; the UI masks secrets.

How deep does compose discovery go?

Root plus nested compose within a shallow depth (including common nested layouts). Nested compose -f is supported for logs and stack actions.

Download for macOS GitHub