Appearance
Linux standalone
This guide uses /opt/openrp-framework and a dedicated openrp service account. It does not require Docker or EasyPanel.
Prepare the host
Install MariaDB, Node.js 22.12+, npm and sampctl. Use Linux open.mp and Linux versions of every required component/plugin. Follow the official Linux runtime instructions for the 32-bit libraries required on your distribution.
For Debian/Ubuntu, the official guide includes enabling i386 and installing the relevant 32-bit runtime libraries. Other plugin requirements depend on the builds you obtain. Check them individually:
sh
file ./omp-server
ldd ./omp-server
ldd plugins/ColAndreas.soResolve not found entries before startup. Do not rename a Windows DLL to .so. Create a non-root service account and give it the game directory and writable runtime folders.
Configure and test
Complete the database, build, web and agent guides. Use forward-slash, case-correct paths. The collision path is exactly:
text
/opt/openrp-framework/scriptfiles/colandreas/ColAndreas.cadbFor a foreground test, from the game root:
sh
chmod +x omp-server
./omp-serverStop this process before starting it through the agent. The agent environment uses SAMP_BIN=./omp-server and the absolute game directory.
Supervise the agent with systemd
Adapt the shipped web-platform/samp-agent/samp-agent.service. Confirm the Node executable using command -v node; a service does not inherit your interactive Node version-manager setup.
ini
[Unit]
Description=OpenRP Framework server agent
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
User=openrp
WorkingDirectory=/opt/openrp-framework/web-platform/samp-agent
EnvironmentFile=/opt/openrp-framework/web-platform/samp-agent/.env
ExecStart=/usr/bin/node /opt/openrp-framework/web-platform/samp-agent/index.mjs
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.targetSave your adapted unit as /etc/systemd/system/openrp-agent.service, then:
sh
sudo systemctl daemon-reload
sudo systemctl enable --now openrp-agent
sudo systemctl status openrp-agent
sudo journalctl -u openrp-agent -fThe agent starts as a service; start the game using ACP. The agent does not automatically adopt or restart a game process it did not spawn.
Supervise the web app
Build first with npm ci, npm run db:generate and npm run build. Use a separate unit with the web directory as WorkingDirectory and ExecStart=/usr/bin/node scripts/start.mjs. That launcher reads .env.local and runs the prepared standalone server. Run it as the service account, with Restart=on-failure and the same network dependency pattern.
Proxy HTTPS to 127.0.0.1:3000. Preserve the intended hostname/protocol and set AUTH_URL to the public HTTPS origin. Restrict access to the backend so arbitrary clients cannot inject trusted proxy headers.
After reboot
Verify MariaDB, web and agent services. Check the agent status and start the game through ACP. Confirm your service restart policy has not created duplicate game processes. The scheduled-start timer in the web app is in memory and is not a reboot scheduler.
These Linux steps need validation on your actual distribution and plugin builds; they were not executed in the Windows development environment.