game preview modal NOT FINISHED

Author: quinteselena

.github/workflows/release-deploy.yml

@@ -154,5 +154,10 @@ jobs:
           key: ${{ secrets.DEPLOY_KEY }}
           command: |
             wget https://raw.githubusercontent.com/${{ github.repository_owner }}/${{ github.event.repository.name }}/master/docker-compose.yml -O docker-compose.yml
+
+            #To crete the schema of the db in the cloud. 
+            mkdir -p users/src/db
+            wget https://raw.githubusercontent.com/${{ github.repository_owner }}/${{ github.event.repository.name }}/master/users/src/db/init.sql -O ./users/src/db/init.sql
+
             docker compose down
             docker compose up -d --pull always

README.md

@@ -43,7 +43,7 @@ We are a coordinated team working across different layers of the stack to delive
 | :--- | :--- | :--- | 
 | **Elena Quintes** | Frontend| UO269665@uniovi.es | 
 | **Luis Sánchez de Posada** | Frontend| UO277488@uniovi.es | 
-| **Marcos José Sánchez**| Backend | UO300022@uniovi.es | 
+| **Marcos José Hernández**| Backend | UO300022@uniovi.es | 
 | **David Alonso** | Frontend | UO300569@uniovi.es | 
 | **Ceyda Tolunay** | Backend | UO318869@uniovi.es | 
 | **Lucas Uña García** | Backend | UO302165@uniovi.es | 

docker-compose.yml

@@ -80,7 +80,7 @@ services:
 
 networks:
   monitor-net:
-    driver: bridge
+    driver: bridge  
 
 
 

docs/src/04_solution_strategy.adoc

@@ -48,6 +48,10 @@ endif::arc42help[]
 | **Ranking System**
 | **Winrate Metric**
 | Focuses on the win/loss ratio to provide a simple but competitive ranking for the leaderboard.
+
+| **Game State Persistence**
+| **Dedicated 'game_saves' table**
+| To prevent database saturation and optimize network traffic, the `matches` table is only accessed at the start and end of a game. Turn-by-turn data and manual saves are isolated in a dedicated `game_saves` table, keeping the main matches metadata clean and fast.
 |===
 
 === Organizational & Development Strategy

docs/src/06_runtime_view.adoc

@@ -55,9 +55,15 @@ loop
     break There is a winner!
         WebApp --> User: Shows result of the game
     end
+
     WebApp -> GameYEngine: Sends the board state & Asks the bot to play
     GameYEngine --> WebApp: Returns the play of the bot 
     WebApp --> User: Shows the play of the bot
+
+    opt User clicks "Save Game"
+        WebApp -> Db: Upsert current state into game_saves
+        Db --> WebApp: Confirm save
+    end
 end
 
 WebApp -> UsersService: Asks to save the data of the game