Merge pull request #1 from CnCNet/feature/build

Feature/build

Author: Sneer-ra2

.dockerignore

@@ -0,0 +1,2 @@
+.github
+build

.github/workflows/cd.yml

@@ -0,0 +1,47 @@
+name: Build
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - 'main'
+    tags:
+      - 'v*'
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Extract metadata (tags, labels)
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ghcr.io/${{ github.repository }}
+          tags: |
+            type=ref,event=branch
+            type=ref,event=pr
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=raw,value=latest,enable={{is_default_branch}}
+
+      - name: Log in to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build and push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: Dockerfile
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}

Dockerfile

@@ -1,20 +1,34 @@
-FROM ubuntu:22.04
-
-ENV DEBIAN_FRONTEND=noninteractive
+# -------- Build Stage --------
+FROM ubuntu:22.04 AS build
 
+# Install build dependencies
 RUN apt-get update && apt-get install -y \
     ca-certificates \
-    build-essential \
     git \
     cmake \
     ninja-build \
     libmysqlcppconn-dev \
-    && rm -rf /var/lib/apt/lists/*
+    g++ \
+    build-essential
+
+COPY . /app
+
+WORKDIR /app/build
+
+# Build your application
+RUN cmake -G Ninja /app && ninja -j $(( $(nproc) / 2 ))
+
+# -------- Runtime Stage --------
+FROM debian:bookworm-slim
+
+# Install only runtime dependencies
+RUN apt-get update && apt-get install -y --no-install-recommends \
+    libmysqlcppconn-dev && \
+    apt-get clean && rm -rf /var/lib/apt/lists/*
 
-RUN git clone https://github.com/CnCNet/cncnet-ladder-elo-computation.git /repos/cncnet-ladder-elo-computation && \
-    mkdir build && \
-    cd build && \
-    cmake -G Ninja /repos/cncnet-ladder-elo-computation && \
-    ninja -j $(( $(nproc) / 2 ))
+# Set workdir and copy the built binary
+WORKDIR /app
+COPY --from=build /app/build/elogen /app/elogen
 
-WORKDIR /build
+# Run it
+ENTRYPOINT ["/app/elogen"]

README.md

@@ -134,53 +134,9 @@ To find the optimal _p_, we ran many simulations, updating ELOs daily and compar
 
 The sweet spot is _p_ = **1.11**, giving reasonably good results in line with expectations.
 
-## FAQ
-
-_This section is still being created._
-
-### What is the deviation?
-
-The **deviation** indicates how accurate or uncertain your rating is. You’ll appear on the list of **active players** if your deviation drops below **60–70** (depending on your rating), and you'll be removed from the list if it rises above around **100**.
-
-To lower your deviation, you need to provide **new information** about your skill level. Continuously beating much weaker opponents (which might boost your rating in other systems) doesn't help here — it's not new information. For example, you’re expected to win more than **99%** of the time against someone **1000 ELO** below you. So winning 20 games in a row against such an opponent won’t improve your rating — it might even **increase** your deviation due to the lack of meaningful data.
-
-That’s one reason why Glicko-2 is hard to exploit. The best way to reduce your deviation is to play a variety of opponents **close to your skill level**.
-
----
-
-### How many points do I gain or lose per game?
-
-**Short answer:** It depends.
-
-Games are submitted to the system in **daily batches**, not individually. Your rating is updated based on your **overall performance** for the day, rather than on a per-game basis. This method provides a more accurate and stable rating.
-
----
-
-### I didn’t care about my rating before, but now I want to take it seriously. Can you reset it?
-
-**No.** Your rating reflects your performance over roughly the **last 200–300 games**. Older games gradually lose their impact.
-
-If you play **50 games a day for a week**, your rating will effectively reset itself through recent performance. The result will be the same as starting from scratch - just without creating a new account.
-
----
-
-### How bad is a loss against a much weaker opponent?
-
-A single loss isn’t a big deal — even if your opponent is far below you in rating. The expected win rate is never 100%, no matter how large the ELO gap is. So if you lose one game against someone **1000 ELO** below you, it's likely just the one game out of 100 that you were expected to lose anyway.
-
-But the **second** loss is much more significant. That result suggests that your strength may have been overestimated, and the system will start adjusting your rating accordingly.
-
----
-
-### How often is the list updated?
-
-The list is updated once per day, with the daily cutoff at UTC+5.
-Your rating — as shown in the all-time leaderboard — reflects your status at the end of the previous day based on that time.
-
 ## Usage on CnCNet
 
-Since ELO computation is processed in batches - to ensure higher accuracy - rather than after each game, this application needs to run once per day.
-The "ELO day" ends at UTC+5 for all players, so the best time to run it is between UTC+5 and UTC+6.
+Since ELO computation is processed in batches - to ensure higher accuracy - rather than after each game, this application needs to run once per day. The "ELO day" ends at UTC+5 for all players, so the best time to run it is between UTC+5 and UTC+6.
 
 During the build of the Docker container, this repository is cloned and the app is compiled.
 
@@ -190,6 +146,16 @@ During the build of the Docker container, this repository is cloned and the app
 docker build -t elogenerator .
 ```
 
+If packages cannot be fetched, change
+
+  RUN apt-get update && apt-get install -y \
+
+to
+
+  RUN apt-get -o Acquire::ForceIPv4=true update && apt-get -o Acquire::ForceIPv4=true install -y \
+
+in the `Dockerfile`.
+
 When running the container, Docker must be provided with the path to the directory containing the rating files.
 This is usually:
 
@@ -217,7 +183,7 @@ You can provide the environment variables `MYSQL_HOST`, `MYSQL_PASSWORD`, `MYSQL
 ### Example 1:
 
 ```bash
-docker run -it --add-host=host.docker.internal:host-gateway -e MYSQL_PASSWORD=pass -e MYSQL_USER=user -v /home/cncnet/cncnet-ladder-api/cncnet-api/storage/app/rating:/data elogenerator /bin/bash -c "cd /build && ./elogen -H host.docker.internal -P 3307 --log-level info -o /data -m ra2"
+docker run -it --add-host=host.docker.internal:host-gateway -e MYSQL_PASSWORD=pass -e MYSQL_USER=user -v /home/cncnet/cncnet-ladder-api/cncnet-api/storage/app/rating:/data elogenerator -H host.docker.internal -P 3306 --log-level info -o /data -m ra2
 ```
 
 This will generate ELO for `ra2` and write the JSON files to `/home/cncnet/cncnet-ladder-api/cncnet-api/storage/app/rating`.
@@ -227,7 +193,51 @@ It connects to MySQL at the given host and port. User and password are provided
 ### Example 2:
 
 ```bash
-docker run -it --add-host=host.docker.internal:host-gateway -e MYSQL_HOST=host.docker.internal -e MYSQL_PORT=3307 -e MYSQL_PASSWORD=pass -e MYSQL_USER=user -v /home/cncnet/cncnet-ladder-api/cncnet-api/storage/app/rating:/data elogenerator /bin/bash -c "cd /build && ./elogen -o /data -m blitz --tournament-games /repos/cncnet-ladder-elo-computation/data/blitz_ra2_worldseries.json"
+docker run -it --add-host=host.docker.internal:host-gateway -e MYSQL_HOST=host.docker.internal -e MYSQL_PORT=3307 -e MYSQL_PASSWORD=pass -e MYSQL_USER=user -v /home/cncnet/cncnet-ladder-api/cncnet-api/storage/app/rating:/data elogenerator -o /data -m blitz --tournament-games blitz_ra2_worldseries.json
 ```
 
-This will generate ELO for blitz, using environment variables only. It also includes the specified tournament game file from the repository.
+This will generate ELO for blitz, using environment variables only. It also includes the specified tournament game file. Since a tournament file is only used for blitz and not updated anymore, the layout of a tournament won't be explained here. Just throw `gameoverlay.cpp` at an AI and it will provide you an example JSON.
+
+
+## FAQ
+
+_This section is still being created._
+
+### What is the deviation?
+
+The **deviation** indicates how accurate or uncertain your rating is. You’ll appear on the list of **active players** if your deviation drops below **60–70** (depending on your rating), and you'll be removed from the list if it rises above around **100**.
+
+To lower your deviation, you need to provide **new information** about your skill level. Continuously beating much weaker opponents (which might boost your rating in other systems) doesn't help here — it's not new information. For example, you’re expected to win more than **99%** of the time against someone **1000 ELO** below you. So winning 20 games in a row against such an opponent won’t improve your rating — it might even **increase** your deviation due to the lack of meaningful data.
+
+That’s one reason why Glicko-2 is hard to exploit. The best way to reduce your deviation is to play a variety of opponents **close to your skill level**.
+
+---
+
+### How many points do I gain or lose per game?
+
+**Short answer:** It depends.
+
+Games are submitted to the system in **daily batches**, not individually. Your rating is updated based on your **overall performance** for the day, rather than on a per-game basis. This method provides a more accurate and stable rating.
+
+---
+
+### I didn’t care about my rating before, but now I want to take it seriously. Can you reset it?
+
+**No.** Your rating reflects your performance over roughly the **last 200–300 games**. Older games gradually lose their impact.
+
+If you play **50 games a day for a week**, your rating will effectively reset itself through recent performance. The result will be the same as starting from scratch - just without creating a new account.
+
+---
+
+### How bad is a loss against a much weaker opponent?
+
+A single loss isn’t a big deal — even if your opponent is far below you in rating. The expected win rate is never 100%, no matter how large the ELO gap is. So if you lose one game against someone **1000 ELO** below you, it's likely just the one game out of 100 that you were expected to lose anyway.
+
+But the **second** loss is much more significant. That result suggests that your strength may have been overestimated, and the system will start adjusting your rating accordingly.
+
+---
+
+### How often is the list updated?
+
+The list is updated once per day, with the daily cutoff at UTC+5.
+Your rating — as shown in the all-time leaderboard — reflects your status at the end of the previous day based on that time.