Files
esh-pfi-infrastructure/playbooks/fv-ml1-diariz.yaml
T

27 lines
1.8 KiB
YAML

# fv-ml1: provision the Diariz pilot (kenhayward/Diariz @ 5a96cade, AGPL-3.0) beside Scriberr. Brokkr's request for
# Prime (2026-10-19, thread 01M5AH9QCVW7ZQ6VVXGWQGFPRS); Prime 1035: GPU 3, with a nightly worker restart ~0300.
# Source: a clean `git archive` of the pin, extracted to /opt/docker/src/diariz-5a96cad (owned by infra-ops).
# The fleet override (stacks/diariz/docker-compose.override.yml) goes beside upstream's compose; /opt/docker/compose/diariz
# is a symlink to that deploy dir. The .env is rendered from the vault separately (stacks/diariz/render-env.sh) and
# piped to the host; it is never on disk on nh3-dev. This playbook does NOT build or start anything.
vars:
src: /opt/docker/src/diariz-5a96cad
steps:
- {name: stage source archive, upload: {src: /tmp/claude-1000/-home-lkraven-development-eshpfi-management/e0be18fd-0734-4786-b933-904f0a74d2a2/scratchpad/diariz-5a96cad.tar.gz, dest: /tmp/diariz-5a96cad.tar.gz, mode: "0644"}}
- name: Extract the pinned source (once)
sudo: true
shell: |
set -e
install -d -o infra-ops -g infra-ops -m 0755 {{src}}
runuser -u infra-ops -- tar -xzf /tmp/diariz-5a96cad.tar.gz -C {{src}}
test -f {{src}}/deploy/docker-compose.yml && rm -f /tmp/diariz-5a96cad.tar.gz
creates: /opt/docker/src/diariz-5a96cad/deploy/docker-compose.yml
- {name: fleet override, upload: {src: stacks/diariz/docker-compose.override.yml, dest: /opt/docker/src/diariz-5a96cad/deploy/docker-compose.override.yml, mode: "0644"}}
- name: /opt/docker/compose/diariz -> the deploy dir
sudo: true
shell: ln -sfn {{src}}/deploy /opt/docker/compose/diariz && ls -ld /opt/docker/compose/diariz
verify:
- name: Source pinned and the override in place
shell: cd {{src}}/deploy && ls docker-compose.yml docker-compose.override.yml && grep -c device_ids docker-compose.override.yml
changed_when: "false"