Skip to content

Use MYSQL instead of SQLite by default #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 7 commits into from
Jul 8, 2025
Merged

Use MYSQL instead of SQLite by default #13

merged 7 commits into from
Jul 8, 2025

Conversation

josecelano
Copy link
Member

@josecelano josecelano commented Jul 8, 2025 •
edited
Loading

Relates to: torrust#66

Use MYSQL instead of SQLite by default.

Subtasks

  • Create a plan to implement the issue
  • Add MYSQL service to Docker Compose config, and make necessary changes to tracker config or env variables to make MySQL the default DB driver.

@josecelano
docs: [#12] add MySQL migration implementation plan
b0b779b 
- 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.
@josecelano josecelano requested a review from da2ce7 July 8, 2025 09:26
@josecelano josecelano self-assigned this Jul 8, 2025
@josecelano josecelano linked an issue Jul 8, 2025 that may be closed by this pull request
Use MYSQL instead of SQLite by default #12
Closed
15 tasks
josecelano added 6 commits July 8, 2025 10:41
@josecelano
docs: [#12] add ADR-003 for MySQL vs MariaDB decision
13f03d8 
- Document rationale for choosing MySQL over MariaDB
- Reference official Torrust Tracker support and testing
- Include technical compatibility considerations
- Update documentation cross-references
@josecelano
feat: [#12] migrate to mysql and update documentation
343aa27
@josecelano
feat: [#12] add healthcheck to mysql service
4b5dc4e
@josecelano
feat: [#12] complete local functionality and persistence tests for mysql
69090dc
@josecelano
feat: [#12] complete VM integration testing with MySQL x86-64-v2 CPU fix
46ac92a 
- 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
@josecelano
docs: [#12] complete Phase 2 documentation updates for MySQL migration
fa296f1 
- 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
@josecelano josecelano marked this pull request as ready for review July 8, 2025 15:02
@josecelano
Copy link
Member Author

ACK fa296f1

@josecelano josecelano merged commit 5b91b30 into main Jul 8, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@da2ce7 da2ce7 Awaiting requested review from da2ce7

Assignees

@josecelano josecelano

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Use MYSQL instead of SQLite by default
1 participant
@josecelano