Outstanding tasks on refresh of the calibration analyses [aka dev] server

[tamuri]

• write file info.txt in commit output directory (e.g. /mnt/tlodev2stg/tlo-dev-fs-2/task-runner/output/2023-11-24_152805_d06d3d4) with two lines:
  • line 1: a git log message with format: git log --pretty=format:"%H%x09%ad%x09%s" --date=iso-strict ${commit_sha1}
  • line 2: URL to action run page on GitHub e.g. https://github.com/UCL/TLOmodel/actions/runs/7256652901
• gzip *.log files from all runs at end of post-processing step
  • check with @tbhallett if we can get rid of (i) module-specific log files (tlo.*.log) (ii) pickled module dataframes (tlo.*.pickle)
• setup webserver on new vm (tlo-dev-vm-1) & make results publically accessible
  • use Caddy webserver - write Caddyfile
  • Ansible playbook to provision server with Caddy
  • open inbound ports 80, 443 on NIC (via Azure)
  • setup DNS record (e.g. analyses.tlomodel.org) - speak to TimH re. GoDaddy record

[tamuri]

The info file is being written in calibration runs whether or not it's a new commit that's running. If it's a commit that's already run, the workfow writes over the original file, meaning the URL to workflow run points to the run that is skipped. (Hope that made sense!)