Processes Configuration
Processes
Background processes can be deployed and managed by Cloud 66. Any process in a Procfile
will be picked up, deployed and monitored by the system.
If you would like more flexibility over the signals used to control the processes, you can use the procfile_metadata
section. Here is an example:
In this example, a process called worker
is stopped using a TTIN
signal first. After waiting for 120 seconds, if the process is still running, a TERM
signal will be sent. If it is still running after 5 seconds, it will be killed.
As for web
or custom_web
processes, you can specify a restart_signal
which will be sent to the process serving web. This is useful for web servers that can do "phased" or zero-downtime restarts.
All processes restart during each redeployment of the application. If you want to avoid this, you can set restart_on_deploy
to false
.
The default values for process signals depend on which web server and/or process manager you are using.
For the default signals for web servers, click the links below:
For non-web processes:
Process Signal Options
stop_sequence
Defines the sequence of signals sent to stop a process. Format: signal, wait_time, signal, wait_time, ...
Example:
This sends TERM, waits 30 seconds, sends INT, waits 10 seconds, then sends KILL.
restart_signal
Specifies a single signal to restart the process (useful for zero-downtime restarts).
Example:
restart_on_deploy
Controls whether the process restarts during deployment.
Example: