Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Commit cc8165d

Browse files
committed
docs: [#refactor] update repo references and branding to 'Torrust Tracker Deploy'\n\n- Update all documentation and badges to use new repo name and location\n- Replace 'Torrust Tracker Demo' with 'Torrust Tracker Deploy' in README.md and related docs\n- Update .git/config and logs for new remote\n- No changes to VM/directory names or variables (pending user direction)\n- Update proof-of-concepts.md to reflect new repo name in PoC list
1 parent 0ddb604 commit cc8165d

File tree

5 files changed

+20
-20
lines changed

5 files changed

+20
-20
lines changed

.github/copilot-instructions.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@
5353
>
5454
> - No new features or major refactors will be implemented here.
5555
> - Active engineering has moved to a **greenfield redesign initiative** documented under
56-
> `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-demo/issues/31)).
56+
> `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-deploy-bash-poc/issues/31)).
5757
> - Only documentation, requirements, and architecture specification updates are accepted in
5858
> this repo.
5959
>
@@ -78,7 +78,7 @@ This PoC still demonstrates a full twelve-factor style deployment (infrastructur
7878
- Migrating the database from SQLite to MySQL
7979
- Implementing Infrastructure as Code for reproducible deployments
8080

81-
**Current Focus**: Active engineering has moved to a **greenfield redesign initiative** documented under `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-demo/issues/31)). This repository is now frozen and serves as a historical reference.
81+
**Current Focus**: Active engineering has moved to a **greenfield redesign initiative** documented under `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-deploy-bash-poc/issues/31)). This repository is now frozen and serves as a historical reference.
8282

8383
## 🏗️ Twelve-Factor Architecture
8484

@@ -125,7 +125,7 @@ This project implements a complete twelve-factor app architecture with clear sep
125125
## 📁 Repository Structure
126126

127127
```text
128-
torrust-tracker-demo/
128+
torrust-tracker-deploy-bash-poc/
129129
├── .editorconfig # Editor configuration
130130
├── .github/
131131
│ ├── workflows/ # GitHub Actions CI/CD pipelines
@@ -270,8 +270,8 @@ Comprehensive deployment, configuration, and testing guides are available in `do
270270

271271
```bash
272272
# 1. Clone and setup
273-
git clone https://github.com/torrust/torrust-tracker-demo.git
274-
cd torrust-tracker-demo
273+
git clone https://github.com/torrust/torrust-tracker-deploy-bash-poc.git
274+
cd torrust-tracker-deploy-bash-poc
275275

276276
# 2. Install dependencies (Ubuntu/Debian)
277277
make install-deps
@@ -683,7 +683,7 @@ The project implements intelligent sudo cache management to improve the user exp
683683
make infra-destroy # Clean up
684684
```
685685

686-
7. **Review existing issues**: Check [GitHub Issues](https://github.com/torrust/torrust-tracker-demo/issues) for good first contributions
686+
7. **Review existing issues**: Check [GitHub Issues](https://github.com/torrust/torrust-tracker-deploy-bash-poc/issues) for good first contributions
687687

688688
### For Infrastructure Changes
689689

@@ -737,9 +737,9 @@ Be mindful of the execution context for different types of commands. The project
737737

738738
- **`make` commands**: (e.g., `make help`, `make infra-status`) must be run from the project root directory.
739739
- **OpenTofu commands**: (e.g., `tofu init`, `tofu plan`, `tofu apply`) must be run from the `infrastructure/terraform/` directory.
740-
- **Docker Compose commands**: (e.g., `docker compose up -d`, `docker compose ps`) are intended to be run _inside the deployed virtual machine_, typically from the `/home/torrust/github/torrust/torrust-tracker-demo/application` directory.
740+
- **Docker Compose commands**: (e.g., `docker compose up -d`, `docker compose ps`) are intended to be run _inside the deployed virtual machine_, typically from the `/home/torrust/github/torrust/torrust-tracker-deploy-bash-poc/application` directory.
741741

742-
**IMPORTANT**: Always be aware of the current working directory. The repository location `~/Documents/git/committer/me/github/torrust/torrust-tracker-demo` is used in documentation as an example, but contributors may have the project cloned elsewhere. Verify the current location before executing commands.
742+
**IMPORTANT**: Always be aware of the current working directory. The repository location `~/Documents/git/committer/me/github/torrust/torrust-tracker-deploy-bash-poc` is used in documentation as an example, but contributors may have the project cloned elsewhere. Verify the current location before executing commands.
743743

744744
#### Working with Remote Terminals
745745

@@ -777,7 +777,7 @@ and snapshot purposes.
777777

778778
```bash
779779
# Correct way to run Docker Compose commands on remote server
780-
ssh torrust@<VM_IP> "cd /home/torrust/github/torrust/torrust-tracker-demo/application && \
780+
ssh torrust@<VM_IP> "cd /home/torrust/github/torrust/torrust-tracker-deploy-bash-poc/application && \
781781
docker compose --env-file /var/lib/torrust/compose/.env ps"
782782
783783
# Check service status

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
[![Testing](https://github.com/torrust/torrust-tracker-demo/actions/workflows/testing.yml/badge.svg)](https://github.com/torrust/torrust-tracker-demo/actions/workflows/testing.yml)
1+
[![Testing](https://github.com/torrust/torrust-tracker-deploy-bash-poc/actions/workflows/testing.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deploy-bash-poc/actions/workflows/testing.yml)
22

3-
# Torrust Tracker Demo (Frozen Proof of Concept)
3+
# Torrust Tracker Deploy (Frozen Proof of Concept)
44

55
> ⚠️ REPOSITORY STATUS: **This repository is now FROZEN as a historical Proof of Concept (PoC).**
66
>
77
> - No new features or major refactors will be implemented here.
88
> - Active engineering has moved to a **greenfield redesign initiative** documented under
9-
> `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-demo/issues/31)).
9+
> `docs/redesign/` ([Issue #31](https://github.com/torrust/torrust-tracker-deploy-bash-poc/issues/31)).
1010
> - Only documentation, requirements, and architecture specification updates are accepted in
1111
> this repo.
1212
>
@@ -18,7 +18,7 @@ being actively curated to extract reusable requirements for the next-generation
1818

1919
Historic description (legacy context retained below for reference):
2020

21-
This repo contains all the configuration needed to run the live Torrust Tracker demo.
21+
This repo contains all the configuration needed to run the live Torrust Tracker Deploy.
2222

2323
> (Legacy notice) We were in the process of
2424
> [splitting the Torrust Demo repo into two repos](https://github.com/torrust/torrust-demo/issues/79).

docs/redesign/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ useful for future contributors.
1111
This repository serves as the **specification and design phase** for the new production
1212
system. Here's the complete transition plan:
1313

14-
### 1. **Current Repository (`torrust-tracker-demo`)**
14+
### 1. **Current Repository (`torrust-tracker-deploy-bash-poc`)**
1515

16-
- **Final Status**: Will be archived as `torrust-tracker-demo-poc`
16+
- **Final Status**: Will be archived as `torrust-tracker-deploy-bash-poc-poc`
1717
- **Purpose**: Historical reference and complete specification for new system
1818
- **Contains**: Complete documentation through Phase 4 (Goals → Requirements → Analysis → Design → Planning)
1919
- **Role**: Blueprint and specification source for the new implementation
@@ -96,7 +96,7 @@ After a quick review we move to Phase 2 (measure current behaviour: performance,
9696

9797
## Related
9898

99-
- Master issue: [#31 – Redesign](https://github.com/torrust/torrust-tracker-demo/issues/31)
99+
- Master issue: [#31 – Redesign](https://github.com/torrust/torrust-tracker-deploy-bash-poc/issues/31)
100100

101101
## Exceptional Changes (none)
102102

infrastructure/docs/local-testing-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,8 +208,8 @@ The deployed VM includes:
208208
```bash
209209
ssh torrust@<VM_IP>
210210
cd /home/torrust/github/torrust
211-
git clone https://github.com/torrust/torrust-tracker-demo.git
212-
cd torrust-tracker-demo
211+
git clone https://github.com/torrust/torrust-tracker-deploy-bash-poc.git
212+
cd torrust-tracker-deploy-bash-poc
213213
```
214214

215215
### 2. Set up Environment

infrastructure/docs/quick-start.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,8 +112,8 @@ Inside the VM:
112112
```bash
113113
# Clone the repository
114114
cd /home/torrust/github/torrust
115-
git clone https://github.com/torrust/torrust-tracker-demo.git
116-
cd torrust-tracker-demo
115+
git clone https://github.com/torrust/torrust-tracker-deploy-bash-poc.git
116+
cd torrust-tracker-deploy-bash-poc
117117

118118
# Set up environment
119119
cp .env.production .env

0 commit comments

Comments
 (0)