Running SeeKi

SeeKi is a single binary. It reads its config, connects to the database, and serves a local web UI. No daemon manager is required to try it — you run it, you open a browser, you close the terminal when you're done.

Start it

From the directory that contains your seeki.toml:

./seeki

On the first line of output, SeeKi prints the address it is listening on:

INFO seeki: SeeKi listening on http://127.0.0.1:3141

Open that URL in a browser. That's it.

Default port

SeeKi listens on 127.0.0.1:3141 by default. The port number is a small nod to π — easy to remember, unlikely to collide with common dev servers.

Change the port

Set server.host and server.port in your config file:

[server]
host = "127.0.0.1"
port = 8080

Restart the binary and it will bind to the new address. If you bind to 0.0.0.0 the UI becomes reachable from other machines on your network — keep in mind that SeeKi has no authentication layer of its own, so only do that on a trusted network.

Foreground vs. background

Two honest options, depending on how long you want it running.

Foreground — for a session

Run it in a terminal. Press Ctrl + C to stop. Logs go to stdout where you can watch them. This is the right choice when you're exploring data for an hour or two.

systemd — for a long-lived install

If you want SeeKi to come back up after a reboot, a small user-level systemd unit is usually all you need. Save this as ~/.config/systemd/user/seeki.service:

[Unit]
Description=SeeKi — read-only database browser
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
WorkingDirectory=%h/seeki
ExecStart=%h/seeki/seeki
Restart=on-failure
RestartSec=3
Environment=RUST_LOG=seeki=info

[Install]
WantedBy=default.target

Enable and start it:

systemctl --user daemon-reload
systemctl --user enable --now seeki
systemctl --user status seeki

Tip

WorkingDirectory matters — SeeKi looks for seeki.toml in the current directory first. Point this at the folder that holds your config.

Stopping cleanly

SeeKi is read-only. There is no write queue to flush, no cache to persist, no transaction to roll back. A Ctrl + C or systemctl --user stop seeki is all it takes. Open connections to the database are closed in the background.