This directory contains documentation about issues found in the Torrust Tracker itself during deployment testing, not issues with this deployer application.
When testing the deployer, we sometimes discover issues, limitations, or unexpected behaviors in the Torrust Tracker container or application. This folder documents those findings for reference and potential upstream fixes in the tracker repository.
IN SCOPE (belongs here):
- Tracker container behavior issues
- Tracker configuration problems
- Tracker entrypoint script issues
- Tracker application bugs discovered during deployment
- Tracker API inconsistencies
- Tracker database driver issues
OUT OF SCOPE (belongs elsewhere):
- Deployer bugs → GitHub Issues in this repository
- Infrastructure provisioning issues →
docs/external-issues/github-actions/ordocs/contributing/known-issues.md - Template rendering problems → Code fixes in
src/infrastructure/templating/ - Ansible playbook issues → Code fixes in
templates/ansible/
Each issue should be documented with:
- Problem Description: Clear explanation of the issue
- Root Cause: Analysis of why it happens
- Impact: How it affects deployments
- Current Workaround: How we handle it in the deployer
- Recommended Solution: Proposed fix for the tracker repository
- References: Links to relevant tracker repo files or issues
database-driver-double-specification.md- Tracker requires database driver in both config file and environment variable