refactor: update repository references and rename to Torrust Tracker Deploy

josecelano · josecelano · commit ae49fb520cfc · 2025-09-03T11:02:35.000+01:00
- Update git remote from josecelano/torrust-testing-infra-poc to torrust/torrust-tracker-deploy-rust-poc
- Rename project from 'Torrust Testing Infrastructure' to 'Torrust Tracker Deploy'
- Update package name in Cargo.toml from torrust-testing-infra to torrust-tracker-deploy
- Update all documentation references to reflect new repository location and purpose
- Update source code strings and descriptions to match new project focus
- Update GitHub Actions badge URLs in README.md
- Update contributing documentation references
- Update decision records and research documents
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
@@ -1,8 +1,8 @@
-# Torrust Testing Infrastructure - AI Assistant Instructions
+# Torrust Tracker Deploy - AI Assistant Instructions
 
 ## 📋 Project Overview
 
-This is a testing infrastructure proof-of-concept for the Torrust ecosystem. It uses OpenTofu (Terraform), Ansible, and Rust to provision and manage testing environments with LXD containers and Multipass VMs.
+This is a deployment infrastructure proof-of-concept for the Torrust ecosystem. It uses OpenTofu (Terraform), Ansible, and Rust to provision and manage deployment environments with LXD containers and Multipass VMs.
 
 ## 🏗️ Tech Stack
 
diff --git a/Cargo.toml b/Cargo.toml
@@ -1,12 +1,12 @@
 [package]
-name = "torrust-testing-infra"
+name = "torrust-tracker-deploy"
 version = "0.1.0"
 edition = "2021"
-description = "Torrust Testing Infrastructure with Ansible and OpenTofu"
+description = "Torrust Tracker Deployment Infrastructure with Ansible and OpenTofu"
 license = "MIT"
-default-run = "torrust-testing-infra"
+default-run = "torrust-tracker-deploy"
 [[bin]]
-name = "torrust-testing-infra"
+name = "torrust-tracker-deploy"
 path = "src/main.rs"
 [[bin]]
 name = "e2e-tests"
diff --git a/README.md b/README.md
@@ -1,8 +1,8 @@
-[![Linting](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/linting.yml/badge.svg)](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/linting.yml) [![E2E Tests](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-e2e.yml/badge.svg)](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-e2e.yml) [![Test LXD Container Provisioning](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-lxd-provision.yml/badge.svg)](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-lxd-provision.yml) [![Test Multipass VM Provisioning](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-multipass-provision.yml/badge.svg)](https://github.com/josecelano/torrust-testing-infra-poc/actions/workflows/test-multipass-provision.yml)
+[![Linting](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/linting.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/linting.yml) [![E2E Tests](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-e2e.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-e2e.yml) [![Test LXD Container Provisioning](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-lxd-provision.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-lxd-provision.yml) [![Test Multipass VM Provisioning](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-multipass-provision.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deploy-rust-poc/actions/workflows/test-multipass-provision.yml)
 
-# Torrust Testing Infrastructure
+# Torrust Tracker Deploy
 
-This Rust application provides automated testing infrastructure for Torrust projects. It manages VM provisioning and
+This Rust application provides automated deployment infrastructure for Torrust tracker projects. It manages VM provisioning and
 cloud-init execution using different virtualization approaches, with the goal of finding the best solution for
 creating VMs that support cloud-init both locally (development) and in CI environments (GitHub Actions).
 
@@ -52,7 +52,7 @@ This repository tests two different virtualization technologies:
 
 ### Prerequisites
 
-This is a Rust application that automates testing infrastructure deployment using OpenTofu and Ansible.
+This is a Rust application that automates deployment infrastructure using OpenTofu and Ansible.
 
 Install the required tools:
 
@@ -94,7 +94,7 @@ cargo run
 
 # Or install and run directly
 cargo install --path .
-torrust-testing-infra
+torrust-tracker-deploy
 ```
 
 #### Development Tasks
@@ -226,7 +226,7 @@ The repository includes comprehensive GitHub Actions workflows for CI testing:
 - [x] Docker installation playbook
 - [x] Docker Compose installation playbook
 - [x] Automated testing workflows
-- [x] End-to-End (E2E) testing infrastructure and workflows
+- [x] End-to-End (E2E) deployment infrastructure and workflows
 
 ### 🔄 In Progress
 
diff --git a/docs/contributing/README.md b/docs/contributing/README.md
@@ -51,8 +51,8 @@ git push origin 42-add-your-feature-name
 
 ## 🤝 Getting Help
 
-- **Issues**: Check existing [GitHub issues](https://github.com/josecelano/torrust-testing-infra-poc/issues)
-- **Discussions**: Start a [GitHub discussion](https://github.com/josecelano/torrust-testing-infra-poc/discussions)
+- **Issues**: Check existing [GitHub issues](https://github.com/torrust/torrust-tracker-deploy-rust-poc/issues)
+- **Discussions**: Start a [GitHub discussion](https://github.com/torrust/torrust-tracker-deploy-rust-poc/discussions)
 - **Documentation**: Review the [docs folder](../) for detailed information
 
 Thank you for contributing! 🎉
diff --git a/docs/contributing/branching.md b/docs/contributing/branching.md
@@ -1,6 +1,6 @@
 # Branching Conventions
 
-This document outlines the branching conventions for the Torrust Testing Infrastructure project.
+This document outlines the branching conventions for the Torrust Tracker Deploy project.
 
 ## 🌿 Branch Naming
 
diff --git a/docs/contributing/commit-process.md b/docs/contributing/commit-process.md
@@ -1,6 +1,6 @@
 # Commit Process and Pre-commit Checks
 
-This document outlines the commit process, including required pre-commit checks and conventions for the Torrust Testing Infrastructure project.
+This document outlines the commit process, including required pre-commit checks and conventions for the Torrust Tracker Deploy project.
 
 ## 📝 Conventional Commits
 
diff --git a/docs/contributing/linting.md b/docs/contributing/linting.md
@@ -1,6 +1,6 @@
 # Linting Conventions and Tools
 
-This document covers the linting tools, configurations, and conventions used in the Torrust Testing Infrastructure project.
+This document covers the linting tools, configurations, and conventions used in the Torrust Tracker Deploy project.
 
 ## 🔧 Linting Tools Overview
 
diff --git a/docs/decisions/docker-testing-rejection.md b/docs/decisions/docker-testing-rejection.md
@@ -7,7 +7,7 @@
 
 ## Context and Problem Statement
 
-During the development of the Torrust Testing Infrastructure project, we needed to establish a testing strategy for Ansible playbooks. The initial hypothesis was that Docker containers could provide faster testing cycles compared to full VMs or LXD containers, potentially offering significant development velocity improvements.
+During the development of the Torrust Tracker Deploy project, we needed to establish a testing strategy for Ansible playbooks. The initial hypothesis was that Docker containers could provide faster testing cycles compared to full VMs or LXD containers, potentially offering significant development velocity improvements.
 
 The core question was: **Should we use lightweight Docker containers for Ansible playbook testing to achieve faster feedback loops?**
 
@@ -17,7 +17,7 @@ The core question was: **Should we use lightweight Docker containers for Ansible
 - **Resource Efficiency**: Lower resource consumption for CI/CD pipelines
 - **Comprehensive Testing**: Need to test both infrastructure and application deployment playbooks
 - **Production Parity**: Test environment should behave like production cloud VMs
-- **Maintenance Overhead**: Simpler testing infrastructure reduces long-term costs
+- **Maintenance Overhead**: Simpler deployment infrastructure reduces long-term costs
 
 ## Considered Options
 
@@ -71,7 +71,7 @@ The core question was: **Should we use lightweight Docker containers for Ansible
 **Cons**:
 
 - Increased maintenance complexity
-- Dual testing infrastructure
+- Dual deployment infrastructure
 - Potential inconsistencies between environments
 
 ## Decision Outcome
diff --git a/docs/research/ansible-testing-strategy.md b/docs/research/ansible-testing-strategy.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-This document outlines the testing strategy for Ansible playbooks in the Torrust Testing Infrastructure project. Based on comprehensive research comparing Docker containers vs LXD containers, we have established an LXD-exclusive approach for all Ansible testing.
+This document outlines the testing strategy for Ansible playbooks in the Torrust Tracker Deploy project. Based on comprehensive research comparing Docker containers vs LXD containers, we have established an LXD-exclusive approach for all Ansible testing.
 
 ## Updated Strategy (September 2025)
 
diff --git a/docs/research/docker-vs-lxd-ansible-testing.md b/docs/research/docker-vs-lxd-ansible-testing.md
@@ -542,7 +542,7 @@ time ansible-playbook -i inventory-docker.yml deploy-app-config.yml       # 4.6s
 
 ## Final Recommendation
 
-**Use LXD exclusively for all Ansible playbook testing** in the Torrust Testing Infrastructure project because:
+**Use LXD exclusively for all Ansible playbook testing** in the Torrust Tracker Deploy project because:
 
 1. ✅ **Complete functionality**: Supports all required features (systemd, Docker daemon, networking)
 2. ✅ **Real testing**: Can validate actual service deployment and functionality
diff --git a/docs/vm-providers.md b/docs/vm-providers.md
@@ -1,10 +1,10 @@
 # VM Providers Comparison: LXD vs Multipass
 
-This document provides a detailed comparison between LXD containers and Multipass VMs for the Torrust testing infrastructure, explaining why LXD was chosen as the official provider.
+This document provides a detailed comparison between LXD containers and Multipass VMs for the Torrust tracker deployment infrastructure, explaining why LXD was chosen as the official provider.
 
 ## 🔄 Overview
 
-For the Torrust testing infrastructure, we evaluated two main approaches for creating virtual environments that support cloud-init:
+For the Torrust tracker deployment infrastructure, we evaluated two main approaches for creating virtual environments that support cloud-init:
 
 1. **LXD Containers** - System containers with cloud-init support
 2. **Multipass VMs** - Full virtual machines with nested virtualization
diff --git a/src/bin/e2e_tests.rs b/src/bin/e2e_tests.rs
@@ -10,7 +10,7 @@ use tokio::time::sleep;
 
 #[derive(Parser)]
 #[command(name = "e2e-tests")]
-#[command(about = "E2E tests for Torrust Testing Infrastructure")]
+#[command(about = "E2E tests for Torrust Tracker Deploy")]
 struct Cli {
     /// Test to run
     #[arg(value_enum)]
@@ -400,7 +400,7 @@ async fn test_wait_cloud_init(env: &TestEnvironment) -> Result<()> {
 async fn main() -> Result<()> {
     let cli = Cli::parse();
 
-    println!("🚀 Torrust Testing Infrastructure E2E Tests");
+    println!("🚀 Torrust Tracker Deploy E2E Tests");
     println!("===========================================");
 
     let env = TestEnvironment::new(cli.keep, cli.verbose)?;
diff --git a/src/main.rs b/src/main.rs
@@ -1,15 +1,15 @@
 fn main() {
-    println!("🏗️  Torrust Testing Infrastructure");
-    println!("=================================");
+    println!("🏗️  Torrust Tracker Deploy");
+    println!("=========================");
     println!();
-    println!("This repository provides automated testing infrastructure for Torrust projects.");
+    println!("This repository provides automated deployment infrastructure for Torrust tracker projects.");
     println!("The infrastructure includes VM provisioning with OpenTofu and configuration");
     println!("management with Ansible playbooks.");
     println!();
     println!("📋 Getting Started:");
     println!("   Please follow the instructions in the README.md file to:");
     println!("   1. Set up the required dependencies (OpenTofu, Ansible, LXD)");
-    println!("   2. Provision the testing infrastructure");
+    println!("   2. Provision the deployment infrastructure");
     println!("   3. Deploy and configure the services");
     println!();
     println!("🧪 Running E2E Tests:");
