80f810fb0c
Complete rewrite of the semaphore role. Supersedes three prior
iterations whose admin-user-creation logic was unreliable across
Semaphore CLI versions.
Architecture:
- Rootful Podman Quadlet under /etc/containers/systemd/
- Separate PostgreSQL 16-alpine container on a user-defined
podman network (semaphore-net)
- Named volumes for both data stores (semaphore_data,
semaphore_postgres_data) so container recreation is
non-destructive
- Pinned image tags: semaphoreui/semaphore:v2.18.5-ansible2.16.5
and postgres:16-alpine
- Post-deploy HTTP health check fails the playbook if Semaphore
doesn't respond on /api/ping within ~60s
Admin user creation remains intentionally manual after first deploy;
the role README documents the exact podman exec command.
Removes the duplicate deploy_semaphore.yml and the now-unneeded
cleanup_semaphore.yml; day1_deploy_semaphore.yml is the canonical
entry point.
18 lines
624 B
YAML
18 lines
624 B
YAML
---
|
|
# ============================================================================
|
|
# day1_deploy_semaphore.yml
|
|
# ----------------------------------------------------------------------------
|
|
# Deploys SemaphoreUI + PostgreSQL on the imagineering host (figment).
|
|
# Run AFTER day0_linux_baseline.yml has been applied to the target.
|
|
#
|
|
# Usage:
|
|
# ansible-playbook -i inventory.yml playbooks/day1_deploy_semaphore.yml
|
|
# ============================================================================
|
|
|
|
- name: Deploy SemaphoreUI on imagineering
|
|
hosts: semaphore_server
|
|
become: true
|
|
gather_facts: true
|
|
roles:
|
|
- semaphore
|