Skip to main content

​
Introduction

Laravel Forge uses Supervisor to manage background processes, ensuring your long-running scripts stay active. This is particularly useful for maintaining daemons like ReactPHP applications. When a process stops unexpectedly, Supervisor automatically restarts it to maintain continuous operation.

​
Configuring background processes

Background processes can be configured on both a server and site level. To create a background process, navigate to the “Processes” tab on the server or site. Then, click the “Add background process” button. After providing the required fields, click the “Create background process” button. When creating a new background process, you’ll need to configure the following settings:
  • Name: Provide a descriptive name for the background process to help identify it.
  • Command: Specify the command that the background process should execute. For example: php artisan reverb:start.
  • Working Directory: Set the working directory for your command. This field is optional and can be left empty.
  • User: Choose the operating system user to run the command. The forge user is used by default.
  • Processes: Define how many instances of the process should run simultaneously.
  • Start Seconds: Set the minimum runtime (in seconds) required to consider the process startup successful.
  • Stop Seconds: Specify how long Supervisor waits for a graceful shutdown before forcing termination.
  • Stop Signal: Choose the signal used to terminate the program during shutdown.

​
Manually restarting background processes

You can manually restart any background process using the command sudo -S supervisorctl restart daemon-{id}:*, where {id} represents the background process’s unique identifier. For instance, to restart a background process with ID 65654, you would run sudo -S supervisorctl restart daemon-65654:*. This command can also be integrated into your deployment scripts to restart background processes automatically during deployments.

​
Log files

Laravel Forge automatically configures each background process to maintain its own log file within the /home/forge/.forge/ directory. Log files follow the naming convention daemon-*.log.
When using Laravel Forge’s user isolation features, daemon log files are located in the .forge directory within /home/{username}, where {username} corresponds to the user assigned to run the process.