biba-deployment

Automate docker-compose deployments on a robot by running the bbupdate workflow to pull the latest GitHub changes, update the GHCR image, and restart the stack. This enforces a prescribed CI gate and avoids ad-hoc manual edits.

The best way to safely update GHCR images and restart a robot stack is using the bbupdate workflow, which applies safeguards before updating and guides post-deploy verification to confirm the correct revision and a healthy stack.

Your robot deployment requires pulling from GitHub to ensure deployments come from a tracked source and avoid ad-hoc manual repo edits. The bbupdate workflow enforces this CI gate to keep deployments safe and repeatable.

Yes, you can trigger remote robot deployments and verify the correct revision afterwards. The workflow provides safe remote invocation considerations and enforces post-deploy verification steps to confirm the stack is healthy.

Yes, the bbupdate workflow supports restarting the docker-compose stack. It automates pulling the latest GitHub changes, updates the GHCR image, and restarts the stack with built-in safeguards and post-deploy checks.

Limitations for remote invocation include strictly following the prescribed CI gate and avoiding manual repo edits on the robot. The workflow provides guardrails to prevent unsafe edits and requires post-deploy verification to ensure stack health.