Skip to content

hammunition-console

A terminal front end for the engine -- install, station, logs and updates in one full-screen program

Status: retired. Folded into the engine as hammunition console (#302): the console only drives the engine, so a separate repository produced a version floor and a refusal where an update was wanted. Install or update the engine and run hammunition console; sudo apt install python3-urwid (or the console extra in a virtualenv) is its one dependency. The old repository is archived. Recorded 2026-10-04. Verdict tested by us.

What it does

Retired: the standalone v0.1.0 terminal front end, now part of the engine as hammunition console. It is the same full-screen program: Home shows the health check, whether your station is set, the last run and how many units are behind the catalog's pin; Install shows the engine's own plan and then runs the real command in a terminal pane; Station, Logs, Update and Help round it out. Nothing about it is measured over SSH or on a Pi.

Why you would want it

You do not need this unit. Run hammunition console from the engine you already have (reference: docs/console/index.md). This entry stays only so that hammunition uninstall hammunition-console removes what a v0.1.0 install placed.

Before it will work

None for the unit, which cannot be installed. hammunition console needs the engine, python3-urwid (or the console extra in a virtualenv) and a terminal of at least 80x24.

How it installs

  • prebuilt tarball from https://github.com/Renegade-Penguin/hammunition-console/releases/download/v0.1.0/hammunition-console-0.1.0.tar.gz
  • The tag's source tree, installed to /usr/local/share/hammunition/hammunition-console and handed to the operator, with a launcher named hammunition-console in ~/.local/bin and a terminal menu entry. Nothing is built and nothing runs as root but the copy. The console's own configuration, ~/.config/hammunition-console/, is created by the program when it first runs and is left in place on uninstall.

What it changes on your machine

  • installed tree — /usr/local/share/hammunition/hammunition-console is created and handed to the operator who ran the install by an explicit chown step in the plan (D-043): the software keeps settings, logs or data beside its executable, so the tree has to be writable by whoever runs it. On a shared machine that means anyone who can act as that user can change what the launcher runs.
  • /usr/local/share/hammunition stays root-owned; the tree itself is replaced whole on every install, so anything the software wrote inside it is lost then
  • undo: hammunition uninstall hammunition-console removes the tree

Known problems

A copy of the standalone console on PATH (the old unit's tree, or the old repository's per-user install.sh) keeps working until you uninstall it, and hammunition-console is not hammunition console: remove the old one with hammunition uninstall hammunition-console (or that repository's uninstall.sh).

Keeping it current

  • probe: github release (Renegade-Penguin/hammunition-console)
  • strategy: reinstall
  • Tagged releases; each is a new source-archive digest. Re-pin the URL and the digest together at every tag, never from a branch.

Where to get help with the software itself

The old repository is archived. Issues about hammunition console go to the Hammunition repository.

Source: catalog/packages/hammunition-console.yaml