Appearance
Linux with EasyPanel
Recommended production setup. EasyPanel gives you a place to manage services, domains, environment variables, storage and logs. The framework does not require it; standalone Linux remains supported as a deployment approach.
Service layout
| Service | Contents | Exposure |
|---|---|---|
| Database | MariaDB and persistent database storage | Private network |
| Web | Public server website, UCP and ACP | HTTPS domain → container port 3000 |
| Game + agent | Linux open.mp, plugins, runtime files and Node agent | Game UDP; artwork TCP when needed; private agent HTTP |
| Your SMTP provider or separate mail server | Outbound authenticated SMTP from web |
The game and agent must share a process namespace, not just a filesystem mount. Build them into the same service/container when using this layout. Running an agent container beside an independently supervised game container does not give ACP ownership of that game process.
1. Database
Create a MariaDB service, persist its data and record its private hostname. Import the clean schema and create an application user. The SQL selects omprp; align the service/database name with that import. Do not expose the database port to the internet.
2. Web service
Create an App service from your framework source. Use these paths for the existing Dockerfile:
text
Build context / build path: web-platform/
Dockerfile within that context: web/Dockerfile
Container HTTP port: 3000The Dockerfile uses COPY web/...; setting the context to web-platform/web/ will fail. Add the complete web environment through EasyPanel. Use the database service’s private hostname in DATABASE_URL, your public HTTPS origin in AUTH_URL, and a fresh AUTH_SECRET.
The runner already binds to 0.0.0.0:3000. Add a domain targeting port 3000, deploy, then check runtime logs. Do not bake secrets into source or Docker build arguments.
3. First administrator
Run the bootstrap from a trusted checkout/build environment containing the web dependencies and your private database connection. The lean production runner does not include every development/administration script. Do not assume npm run admin:create exists inside the final runner image.
If your database is reachable only privately, use a temporary administration job on that network with the same reviewed source. Remove it after creating the account. Follow bootstrap instructions; never create a public shared password.
4. Game and agent service
Prepare a Linux image containing your compiled gamemode, matching open.mp runtime/plugins, Node.js and the libraries needed by the 32-bit game and native agent dependency. Start the agent as the service process. The framework does not ship a prevalidated universal game/agent image: adapt the Docker layout to your runtime.
Configure:
dotenv
AGENT_BIND=0.0.0.0
AGENT_PORT=7001
SAMP_DIR=/srv/openrp
SAMP_BIN=./omp-server
SAMP_HOST=127.0.0.1
SAMP_PORT=7777
SAMP_AGENT_KEY=YOUR_SHARED_RANDOM_AGENT_KEYSet the web app’s SAMP_AGENT_URL to the service’s private HTTP address and use the same agent key. For query status, set SAMP_QUERY_HOST to the private game-service hostname and RCON_PORT to its game UDP port. Neither container uses the other’s localhost.
5. Ports and persistent storage
Publish game UDP 7777, or your chosen game port. Artwork downloads use a separately configured TCP listener; TCP and UDP may use the same numeric port. The agent’s HTTP port stays private. Use one game/agent replica.
Persist game runtime data, generated collision data, uploaded models, relevant logs/configuration and database storage. Do not mount an empty volume over the whole game directory: it would hide the files built into the image. Initialise volumes deliberately or use narrower mounts.
EasyPanel distinguishes HTTP domains from direct TCP/UDP port publishing, and configuration changes generally need deployment to reach the service. See its App service documentation for the current controls.
Acceptance test
Use ACP to start the game, verify logs and connect with a game client. Exercise crate loading, faction lockers and email recovery. Then stop the game cleanly, redeploy and prove that persistent data remains. Test on your chosen Linux image before opening registrations.