kevinveenbirkenbach/computer-playbook
1
0
Fork 0
mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2025-09-11 21:07:16 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
cbfb096cdb165ee8e77fdfeaf8417672ac2a7865
computer-playbook/roles/web-app-jira
History
Kevin Veen-Birkenbach cbfb096cdb Refactor web health checker & domain expectations (filter-based) 
- Move all domain→expected-status mapping to filter `web_health_expectations`.
- Require explicit app selection via non-empty `group_names`; only those apps are included.
- Add `www_enabled` flag (wired via `WWW_REDIRECT_ENABLED`) to generate/force www.* → 301.
- Support `redirect_maps` to include manual redirects (sources forced to 301), independent of app selection.
- Aliases always 301; canonicals use per-key override or `server.status_codes.default`, else [200,302,301].
- Remove legacy fallbacks (`server.status_codes.home` / `landingpage`).
- Wire filter output into systemd ExecStart script as JSON expectations.
- Normalize various templates to use `to_json` and minor spacing fixes.
- Update app configs (e.g., YOURLS default=301; Confluence default=302; Bluesky web=405; MediaWiki/Confluence canonical/aliases).
- Constructor now uses `WWW_REDIRECT_ENABLED` for domain generation.

Tests:
- Add comprehensive unit tests for filter: selection by group, keyed/default codes, aliases, www handling, redirect_maps, input sanitization.
- Add unit tests for the standalone checker script (JSON parsing, OK/mismatch counting, sanitization).

See conversation: https://chatgpt.com/share/68c2b93e-de58-800f-8c16-ea05755ba776
2025-09-11 13:58:16 +02:00
..
config
Refactor web health checker & domain expectations (filter-based)
2025-09-11 13:58:16 +02:00
meta
Confluence/Jira roles: add READMEs, switch to custom images, proxy/JVM envs, and integer-safe heap sizing
2025-09-02 12:07:34 +02:00
schema
Confluence/Jira roles: add READMEs, switch to custom images, proxy/JVM envs, and integer-safe heap sizing
2025-09-02 12:07:34 +02:00
tasks
Confluence/Jira roles: add READMEs, switch to custom images, proxy/JVM envs, and integer-safe heap sizing
2025-09-02 12:07:34 +02:00
templates
Refactor Confluence and Jira env templates to use official Atlassian ATL_* database variables instead of unused custom placeholders. Ensures containers connect directly to PostgreSQL without relying on CONFLUENCE_DATABASE_* or JIRA_DATABASE_* vars. See conversation: https://chatgpt.com/share/68b6ddfd-3c44-800f-a57e-244dbd7ceeb5
2025-09-02 14:07:38 +02:00
vars
Atlassian JVM sizing: cast memory vars to int before floor-division
2025-09-02 13:22:59 +02:00
README.md
Confluence/Jira roles: add READMEs, switch to custom images, proxy/JVM envs, and integer-safe heap sizing
2025-09-02 12:07:34 +02:00

README.md

Jira

Description

Jira Software is Atlassian’s issue and project-tracking platform. This role deploys Jira via Docker Compose, connects it to PostgreSQL, and adds proxy awareness, optional OIDC SSO, health checks, and production-oriented defaults for Infinito.Nexus.

Overview

The role builds a lean custom image on top of the official Jira Software image, provisions persistent volumes, and exposes the app behind your reverse proxy. Variables control image/version/volumes/domains/SSO. JVM heap sizing is auto-derived from host RAM with safe caps to prevent Xms > Xmx.

Features

  • Fully Dockerized: Compose stack with a dedicated data volume (jira_data) and a minimal overlay image to enable future plugins/config.
  • Reverse-Proxy/HTTPS Ready: Preconfigured Atlassian Tomcat proxy envs so Jira respects external scheme/host/port.
  • OIDC SSO (Optional): Pre-templated vars for issuer, client, endpoints, scopes; compatible with Atlassian DC SSO/OIDC marketplace apps.
  • Central Database: PostgreSQL integration (local or central) with credentials sourced from role configuration.
  • JVM Auto-Tuning: Safe calculation of JVM_MINIMUM_MEMORY / JVM_MAXIMUM_MEMORY with caps to avoid VM init errors.
  • Health Checks: Container healthcheck for quicker failure detection and stable automation.
  • CSP & Canonical Domains: Integrates with platform CSP and domain management.
  • Backup Ready: Persistent data under /var/atlassian/application-data/jira.

Further Resources