charly -- OpenCharly CLI binary

Candy Properties

What It Provides

The charly binary inside containers serves two purposes:

1. Native D-Bus agent — charly eval dbus commands on the host delegate to an in-venue charly via engine exec container charly eval dbus <cmd> . <args>, which connects to the local D-Bus session bus using godbus/dbus/v5 (pure Go, no external tools needed). The primary path for charly eval dbus notify, charly eval dbus call, charly eval dbus list, and charly eval dbus introspect. The box need NOT bake the charly candy for this: when the venue lacks charly, the explicit dbus commands COPY the host's own binary in on demand (the generic copy-charly-into-a-running-venue mechanism, EnsureCharlyInVenue over DeployExecutor.PutFile — podman cp for a container, scp for a VM/host) and invoke the delivered copy. Baking the candy only pre-stages the binary so the first call skips the copy.

2. In-container CLI — full charly functionality available inside the container for scripting, service management, and automation.

Eval-vs-production binary source — disposable beds bake the IN-DEV charly