Skip to main content Crate carte Copy item path Source cli The carte command line. client Talks to the daemon over its Unix socket. clock Wall-clock times as people read them. daemon The daemon: supervisor, proxy, DNS and the API socket, until a signal stops it. dns exit The exit codes every command ends with. instance_dirs Creates an instance’s state and run directories, and keeps its stack’s record. kube Kube projects in the daemon: requests for a cluster’s Services go to port-forwards
carte opens on demand and stops once nobody uses them. logs Per-process log storage. loopback Connections to loopback ports. metrics Memory and CPU use of process groups. paths Where carte keeps configuration, state and its socket. process Daemon side of process spawning: every process runs under carte __shim
on a pty (or pipes), holding a lifeline socket to the daemon. process_env The env a process starts with, as carte env and the daemon’s env request show it. proctree The process groups a process’s descendants run in, so stopping a command
also reaches the groups it made for its children. proxy The reverse proxy: accepts HTTP(S) on loopback (HTTP/2 over TLS when the
client offers it), asks a Router127.0.0.1 or ::1, or over a connection a Dialer prune Finds and removes leftover instance directories and pidfiles for carte prune.
Only files: nothing here runs a command. pty System-wide pty capacity, so the supervisor can keep a reserve for the
user’s terminals. rank Ranks lines by how well they match a query, with BM25. setup carte setup: the one-time machine changes, planned as data and shown before they run.shim The carte __shim mode: runs one command in its own process group and
takes the group down when the daemon goes away. supervisor The supervisor owns every instance and process. It runs as one task; everything
else talks to it through a Handle tls tui carte tui: watch and control the daemon.urls URLs and hostnames that templates and injected variables point at: every app in the same stack.