Deployment Overview of Counter-Strike 2 Server on Server¶

Prerequisites and Basic Requirements¶

The deployment of the Counter-Strike 2 server requires the following system specifications and privileges:

Operating System: Ubuntu (specifically utilizing the multiverse repository and support for i386 architecture).
Privileges: Root access or sudo privileges are required to install system packages, manage directories, and execute the server management script.
Dependencies: The steamcmd package must be installed via the apt package manager.
Network: Access to the internet is required for downloading the SteamCMD client and updating the game binaries.

The application and its associated components are organized within specific directories on the server:

The installation process involves setting up the environment, installing SteamCMD, and downloading the Counter-Strike 2 server files.

Repository Configuration: The multiverse repository is added to the APT sources, and the i386 architecture is enabled to support legacy dependencies.
Package Installation: System packages are updated, and the steamcmd package is installed using apt.
Directory Creation: The installation directory /opt/cs2 and the Steam SDK directory /root/.steam/sdk64 are created with 0755 permissions.
SteamCMD Setup: The SteamCMD client is downloaded and extracted into /opt/cs2.
Game Download: The Counter-Strike 2 server (Application ID 730) is downloaded and validated via SteamCMD using the force_install_dir command.
Library Linking: The steamclient.so file is copied from /opt/cs2/linux64/ to /root/.steam/sdk64/ to ensure library compatibility.
Configuration and Scripting: The server configuration file cs2server.cfg is deployed to /opt/cs2/game/game/csgo/cfg/, and the management script cs2server.sh is placed in /root/.

The deployment includes an Nginx container configured for SSL certificate management and proxying.

Container Image: jonasal/nginx-certbot:latest
Network Mode: The container runs in host network mode.
Volume Mounts:
nginx_secrets: An external volume mounted to /etc/letsencrypt.
/data/nginx/user_conf.d: Mounted to /etc/nginx/user_conf.d for custom user configurations.
Environment Variables:
CERTBOT_EMAIL: Set to [email protected].
Additional configuration is loaded from /data/nginx/nginx-certbot.env.

The Nginx container functions as the primary proxy server handling SSL termination and traffic routing.

Functionality: The container utilizes Certbot for automated SSL certificate management.
Secrets Management: SSL secrets are stored in the external Docker volume nginx_secrets.
Configuration: Custom Nginx configurations are expected to be placed in /data/nginx/user_conf.d on the host, which maps directly to the container.

Server operations are managed through the custom shell script located at /root/cs2server.sh. The script accepts the following arguments:

Start: Executes the server binary located at /opt/cs2/game/game/bin/linuxsteamrt64/cs2 with the -dedicated flag and loads the cs2server.cfg configuration. It runs in the background via nohup and writes the process ID to /tmp/cs2server.pid.
Stop: Reads the PID from /tmp/cs2server.pid, terminates the process, and removes the PID file.
Restart: Executes the stop command, waits for 2 seconds, and then executes the start command.
Status: Checks if the PID file exists and verifies if the process is currently running.

Commands to manage the service:

/root/cs2server.sh start
/root/cs2server.sh stop
/root/cs2server.sh restart
/root/cs2server.sh status

File and directory permissions are set during the deployment process to ensure security and functionality:

The following paths contain critical configuration files and runtime data: