You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 10, 2025. It is now read-only.
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
> - Only documentation, requirements, and architecture specification updates are accepted in
58
58
> this repo.
59
59
>
@@ -78,7 +78,7 @@ This PoC still demonstrates a full twelve-factor style deployment (infrastructur
78
78
- Migrating the database from SQLite to MySQL
79
79
- Implementing Infrastructure as Code for reproducible deployments
80
80
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.
82
82
83
83
## 🏗️ Twelve-Factor Architecture
84
84
@@ -125,7 +125,7 @@ This project implements a complete twelve-factor app architecture with clear sep
125
125
## 📁 Repository Structure
126
126
127
127
```text
128
-
torrust-tracker-demo/
128
+
torrust-tracker-deploy-bash-poc/
129
129
├── .editorconfig # Editor configuration
130
130
├── .github/
131
131
│ ├── workflows/ # GitHub Actions CI/CD pipelines
@@ -270,8 +270,8 @@ Comprehensive deployment, configuration, and testing guides are available in `do
@@ -683,7 +683,7 @@ The project implements intelligent sudo cache management to improve the user exp
683
683
make infra-destroy # Clean up
684
684
```
685
685
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
687
687
688
688
### For Infrastructure Changes
689
689
@@ -737,9 +737,9 @@ Be mindful of the execution context for different types of commands. The project
737
737
738
738
-**`make` commands**: (e.g., `make help`, `make infra-status`) must be run from the project root directory.
739
739
-**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.
741
741
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.
743
743
744
744
#### Working with Remote Terminals
745
745
@@ -777,7 +777,7 @@ and snapshot purposes.
777
777
778
778
```bash
779
779
# Correct way to run Docker Compose commands on remote server
0 commit comments