basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    A long instruction gets checks: “expect X, otherwise stop”

    In a long sequence of commands, put explicit checkpoints: “expect X; if not, stop”.

    What a gate looks like

    wc -c < /srv/secrets/app/key            # more than zero, or don't go on
    diff a b && echo "1 OK: same as the repository"

    An OK line stands out in the output. If it’s missing, stop — don’t decide it’s “probably fine”.

    The number in the line (1 OK) shows which gates passed: the output of a long series shows where it stopped.