docs: reorganize docs and add rollbacks section

Author: josecelano

README.md

@@ -6,53 +6,10 @@ Live demo: <https://index.torrust-demo.com/torrents>.
 
 It's also used to track issues in production.
 
-## Setup
+## Documentation
 
-Follow instructions on [Deploying Torrust To Production](https://torrust.com/blog/deploying-torrust-to-production).
-
-You need to also enable a [firewall](./docs/firewall.md).
-
-The application is located in the directory: `/home/torrust/github/torrust/torrust-demo`.
-
-To run docker compose commands you need to cd to the app dir:
-
-```console
-cd /home/torrust/github/torrust/torrust-demo
-```
-
-Sample commands:
-
-- `docker ps`: list containers.
-- `docker compose logs -f`: print all containers' logs.
-- `docker compose logs -f tracker`: print tracker container' logs.
-- `docker compose logs -f tracker | head -n100`: print the first 100 lines in the tracker container log.
-- `docker compose logs -f | grep "ERROR"`: print logs showing only errors.
-
-## Deployment
-
-1. SSH into the server.
-2. Execute the deployment script: `./bin/deploy-torrust-demo.com.sh`.
-3. Execute the smoke tests:
-
-    ```console
-    cargo run --bin udp_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422
-
-    cargo run --bin http_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422
-
-    TORRUST_CHECKER_CONFIG='{
-        "udp_trackers": ["144.126.245.19:6969"],
-        "http_trackers": ["https://tracker.torrust-demo.com"],
-        "health_checks": ["https://tracker.torrust-demo.com/api/health_check"]
-    }' cargo run --bin tracker_checker
-    ```
-
-4. Check the logs of the tracker container to see if everything is working:
-
-    ```console
-    ./share/bin/tracker-filtered-logs.sh
-    ```
-
-## TODO
-
-- Create a workflow for deployments.
-- Automatic deployment when new docker images are available.
+- [Setup](docs/setup.md)
+- [Deployment](docs/deployment.md)
+- [Firewall](docs/firewall.md)
+- [Sample Commands](docs/sample_commands.md)
+- [Rollbacks](docs/rollbacks.md)

docs/deployment.md

@@ -0,0 +1,23 @@
+# Deployment
+
+1. SSH into the server.
+2. Execute the deployment script: `./bin/deploy-torrust-demo.com.sh`.
+3. Execute the smoke tests:
+
+    ```console
+    cargo run --bin udp_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422
+
+    cargo run --bin http_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422
+
+    TORRUST_CHECKER_CONFIG='{
+        "udp_trackers": ["144.126.245.19:6969"],
+        "http_trackers": ["https://tracker.torrust-demo.com"],
+        "health_checks": ["https://tracker.torrust-demo.com/api/health_check"]
+    }' cargo run --bin tracker_checker
+    ```
+
+4. Check the logs of the tracker container to see if everything is working:
+
+    ```console
+    ./share/bin/tracker-filtered-logs.sh
+    ```

docs/rollbacks.md

@@ -0,0 +1,57 @@
+# Rollbacks
+
+If you have a problems after a [deployment](deployment.md), you can rollback to the previous version of the app.
+
+1. SSH into the server.
+
+2. Check the docker images to see the previous version of the app:
+
+    ```console
+    docker images torrust/tracker
+    REPOSITORY        TAG       IMAGE ID       CREATED          SIZE
+    torrust/tracker   develop   b081a7499542   19 minutes ago   133MB
+    torrust/tracker   <none>    7dbdad453cf3   6 hours ago      133MB
+    ```
+
+3. Tag the previous version of the app with a new name (e.g. `rollback`):
+
+    ```console
+    docker tag 7dbdad453cf3 torrust/tracker:rollback
+    ```
+
+    This command tags the image with ID `7dbdad453cf3` as `torrust/tracker:rollback`.
+
+    ```console
+      docker images torrust/tracker
+        REPOSITORY        TAG        IMAGE ID       CREATED          SIZE
+        torrust/tracker   develop    b081a7499542   21 minutes ago   133MB
+        torrust/tracker   rollback   7dbdad453cf3   6 hours ago      133MB
+    ```
+
+    The `rollback` tag now points to the previous version of the app.
+
+4. Edit the `compose.yaml` file to use the new tag:
+
+    Change the line:
+
+    ```yaml
+    image: torrust/tracker:develop
+    ```
+
+    to:
+
+    ```yaml
+    image: torrust/tracker:rollback
+    ```
+
+5. Run the following command to start the previous version of the app:
+
+    ```console
+    docker compose up --build --detach
+    ```
+
+6. Check the logs of the tracker container to see if everything is working:
+
+    ```console
+    ./share/bin/tracker-filtered-logs.sh
+    ```

docs/sample_commands.md

@@ -0,0 +1,7 @@
+# Sample Commands
+
+- `docker ps`: list containers.
+- `docker compose logs -f`: print all containers' logs.
+- `docker compose logs -f tracker`: print tracker container' logs.
+- `docker compose logs -f tracker | head -n100`: print the first 100 lines in the tracker container log.
+- `docker compose logs -f | grep "ERROR"`: print logs showing only errors.

docs/setup.md

@@ -0,0 +1,13 @@
+# Setup
+
+Follow instructions on [Deploying Torrust To Production](https://torrust.com/blog/deploying-torrust-to-production).
+
+You need to also enable a [firewall](./docs/firewall.md).
+
+The application is located in the directory: `/home/torrust/github/torrust/torrust-demo`.
+
+To run docker compose commands you need to cd to the app dir:
+
+```console
+cd /home/torrust/github/torrust/torrust-demo
+```