Worker Processes keep an application running alongside your website — a Node.js app, a Laravel queue, a PHP script or another custom command. This guide covers starting one, managing it, and what it can and cannot be used for.
If the website deploys from GitHub, its worker processes are also shown on the website's GitHub page.
Static websites do not need a worker at all: deploy them and they are served directly by the web server.
Each process appears in a list with its startup command and working directory. Use the menu next to a process to stop, start or restart it — restart after changing configuration or deploying new code.
Click View logs next to a process to see what it is printing. If an app will not start, the log is the first place to look — it usually shows the error.
Worker processes run inside your website's normal resource limits — the same CPU, memory and process allowances as the website itself. On Shared Hosting they suit lightweight applications. If an app is busy all the time or needs a lot of resources, a Managed VPS is the right home for it; talk to us and we will recommend a setup.
If a process will not run because of the hosting environment, open a support ticket with the website name and the process log.
Please note: Go Red Robot supports the hosting environment and deployment tools. Application development, repository configuration and code debugging are not included with hosting support.