4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	01f5805139	fix(ci): serialize CI per ref + tag images at build time (fd race #1093) ... The publish lane raced on the runner's shared docker daemon when two dev pushes landed seconds apart: a concurrent run evicted the freshly-built :<sha> image mid-push, so the post-push `docker tag :<sha> :dev` failed with "No such image" (a flake — a lone re-run went green). Two guards, both matching CI-runner's canonical build workflows: - Workflow-level `concurrency: ci-${{ github.ref }}` with cancel-in-progress:false serializes runs per ref, so no two publishes ever share the daemon. false (not true) because rule 46 requires every push to emit its own immutable :<sha> image — a superseded run must still finish. - Build both the :<sha> and moving (:dev/:latest) tags in one `docker build -t ... -t ...`, then push each. Removes the fragile post-push `docker tag` of an image a concurrent run could have evicted. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CAGR73DUowdVFVvYzLXC5C	2026-07-19 12:52:29 -04:00
bvandeusenandClaude Opus 4.8	fe57dde57b	feat(ci): publish steward image to the registry + remote-deploy compose ... Add the rule-46 image-publish lane: a `publish` job gated on [lint, unit, integration] that builds the runtime Dockerfile in ci-builder and pushes git.fabledsword.com/bvandeusen/steward:<sha> always, :dev on dev and :latest on main. Authenticates with the REGISTRY_TOKEN repo secret (the injected GITHUB_TOKEN lacks write:package). Steward is the first family app to implement the publish lane; mechanics mirror CI-runner's build-ci-python.yml. Add compose.deploy.yml for a persistent remote instance that pulls :dev (no source bind-mounts, persistent app_data+pgdata volumes, bundled Postgres), plus a README "Remote dev instance" runbook and the POSTGRES_PASSWORD env key. Fix .env.example's database URL var to the canonical STEWARD_DATABASE_URL (single underscore) and document the publish lane in ci-requirements.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-05 11:08:43 -04:00
bvandeusenandClaude Opus 4.8	fb579bcf97	feat(ansible): ship ansible in image + allow system-triggered runs (task 545) ... Foundation for the Ansible automation milestone (#37) — makes the existing manual playbook runner actually executable and the schema automation-ready. - pyproject: [ansible] extra (full ansible package, batteries-included, pinned) - Dockerfile: pip install .[ansible]; add openssh-client for remote runs - models/ansible.py + migration 0012: AnsibleRun.triggered_by now nullable so automated (alert/schedule) runs need no human actor - ansible/routes.py + run_detail.html: show 'Triggered by' (username or 'system') - CI: integration lane installs .[dev,ansible]; new tests/integration/ test_ansible_foundation.py runs a real connection:local playbook end-to-end, asserts success+output, and round-trips a NULL-triggered run No extra-vars/limit/credentials/scheduling here — those are their own #37 tasks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-02 11:31:43 -04:00
bvandeusenandClaude Opus 4.8	d925709c77	ci: add Forgejo CI (lint + unit + Postgres integration) + ci-requirements.md ... Single-repo CI now that plugins are bundled in-tree. Three lanes on push to dev/main, modeled on FabledCurator's canonical ci.yml (minus frontend/Redis): - lint: ruff check steward/ plugins/ tests/ (no dep install) - unit: pytest -m 'not integration' — whole current suite (testing=True mocks DB) - integration: postgres:16-alpine service via socket-discovered bridge IP; a boot-and-migrate test creates the real app, running core + all bundled-plugin migrations, then round-trips the DB — guards the folded-in migration graph. Registers the 'integration' pytest marker; adds tests/integration/test_boot.py. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-01 08:37:32 -04:00