This repository was archived by the owner on Oct 10, 2025. It is now read-only.
Merged
Conversation
- Add comprehensive implementation plan for migrating from SQLite to MySQL - Include correct MySQL connection string format (path parameter) - Document automatic database migrations by Torrust Tracker - Add local Docker Compose testing strategy before VM testing - Update docs structure to include issues directory - Fix configuration based on actual Torrust Tracker MySQL driver The plan follows Phase 1 of the Hetzner migration strategy and provides step-by-step implementation guide with proper testing methodology.
15 tasks
- Document rationale for choosing MySQL over MariaDB - Reference official Torrust Tracker support and testing - Include technical compatibility considerations - Update documentation cross-references
- Updated VM CPU model to host-model for x86-64-v2 instruction set support - Completed VM integration testing phase of MySQL migration - Fixed bash quoting in integration testing guide to avoid history expansion - Documented MySQL CPU requirement issue and technical solution - Verified all services running and healthy on VM with MySQL backend - Smoke tested tracker API endpoints successfully
- Added database configuration section to application README - Enhanced environment file with MySQL-specific comments and headers - Updated migration plan to mark Phase 2 as completed - Documented all MySQL configuration details and requirements - Preserved SQLite configurations as legacy/development options - All linting checks pass successfully
Member
Author
|
ACK fa296f1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to: torrust#66
Use MYSQL instead of SQLite by default.
Subtasks