Linux VPS: headless automation
Run supported simulation and validation jobs without a graphical user session.
Read as MarkdownChoose the right mode
Use the Linux AMD64 artifact on an x86_64 VPS. Headless means a command-line workload, not a hidden promise that every graphical assistant feature is available. Check the release's qualified runner and required renderer before dispatching jobs.
Prepare an isolated job
Use an unprivileged dedicated user and a disposable candidate copy of the project. Keep world, controllers and assets together. Supply the documented dependencies and virtual-display/software-renderer prerequisites when required. Do not install unrelated project services or use root to bypass the sandbox.
Observe and cancel
Keep stdout, stderr, exit status, input identity and output paths. A cancelled job must retire its child processes; a timeout is not a successful simulation. Capture bounded measurements and independently inspect results before applying candidate changes to the original project.
Authentication and resources
Local simulation and customer-managed AI are separate capabilities. If a workload needs customer AI, provision a supported secure credential store; never pass tokens in command arguments or logs. Bound concurrent jobs and monitor disk/RAM. Use remote desktop when you need the visual workspace instead.