Dovik

I built Dovik to make local development processes manageable as a group. When several projects each have their own terminal sessions, it becomes difficult to tell which process belongs to which project, whether it is still running and where its output went. Dovik keeps a project registry and brings process control and observation into one local tool.

One process owner

The daemon owns the registry and process lifecycle. A command-line client and an interactive terminal interface work against one source of state.

• Request start, stop and restart operations through a versioned local protocol.
• Read status and logs for the same managed processes.
• Keep process ownership in the daemon instead of individual clients.

Go implementation

I implemented the system in Go, including the daemon protocol, command-line commands and terminal interface. Output collection is bounded, giving users access to process logs without letting a continuously running development service grow an unlimited output buffer.

How I built it

I wrote integration tests for persistence, lifecycle operations, logs and client communication. The project is focused on supervising local development processes, with both human interaction and command-line automation using the same control path. It remains private while development continues.