-
Notifications
You must be signed in to change notification settings - Fork 0
Installation Standalone
The standalone build is self-contained: it bundles its own MariaDB database, so you don't need Docker or a separately installed database server. It's a good fit anywhere you'd rather not run Docker.
Grab the latest release for your platform from the Releases page:
-
Linux (x64) —
RustRconServerManager-Linux-x64-vX.X.X.X.tar.gz -
Windows (x64) —
RustRconServerManager-Windows-x64-vX.X.X.X.zip
Both are fully self-contained — no .NET runtime required, and the bundled MariaDB listens only on 127.0.0.1:3307, isolated from any other MariaDB/MySQL install you may already have running.
Extract the archive, then:
-
Windows: double-click
start.bat(or runstart.ps1in PowerShell). -
Linux: run
./start.sh
The first time you run it, it will:
- Initialize a local MariaDB data directory (
mariadb-data/) - Generate random database/JWT/RCON credentials and store them in
standalone.env - Create the application's database and user
On every run after that, it reuses the same data and credentials.
Once it's running, open http://localhost:5000 in your browser and create your admin account. The first person to open the panel gets to do this, so don't expose the port publicly until you've completed it.
The bundled MariaDB instance listens only on 127.0.0.1:3307 (loopback, custom port). It is started and stopped automatically together with the app — closing the app (Ctrl+C, or closing the console window) shuts the database down too.
Every time you start it, the launcher checks GitHub for a newer release and installs it automatically before starting the app — only the app/ folder is touched, so this can't affect mariadb-data/ or standalone.env. You can turn this off from the app itself, in Panel Settings > Auto-Update.
If auto-update is off (or you'd rather update manually), your data lives in mariadb-data/ and your generated credentials live in standalone.env, both next to the launcher script. Before replacing the folder with a newer release, copy those two out and put them back afterwards so you don't lose your data.
standalone.env is written right at the start of the first run, before the database is actually initialized. If something fails partway through (a crash, closing the window, an error), delete both standalone.env and mariadb-data/ before trying again — otherwise the script will think setup already finished and skip straight to using credentials that were never actually applied to a working database.
If you'd rather point this at a MariaDB/MySQL server you already run, set the ConnectionStrings__DefaultConnection environment variable yourself before starting app/RustRconServerManager.Backend (or .exe on Windows) directly, instead of using the start script — see .env.example in the repository for the other environment variables the app expects (JWT key, RCON encryption key, etc.).
Once you've logged in, head to Adding a Server to connect your first Rust server.