1.7 KiB
Advanced Post-installation Tasks
This page explains some advanced tasks and configuration options that can be performed after the bot installation and may be uselful in some environments.
If you do not know what things mentioned here mean, you probably do not need it.
Configure the bot running as a systemd service
Copy the freqtrade.service file to your systemd user directory (usually ~/.config/systemd/user) and update WorkingDirectory and ExecStart to match your setup.
!!! Note
Certain systems (like Raspbian) don't load service unit files from the user directory. In this case, copy freqtrade.service into /etc/systemd/user/ (requires superuser permissions).
After that you can start the daemon with:
systemctl --user start freqtrade
For this to be persistent (run when user is logged out) you'll need to enable linger for your freqtrade user.
sudo loginctl enable-linger "$USER"
If you run the bot as a service, you can use systemd service manager as a software watchdog monitoring freqtrade bot
state and restarting it in the case of failures. If the internals.sd_notify parameter is set to true in the
configuration or the --sd-notify command line option is used, the bot will send keep-alive ping messages to systemd
using the sd_notify (systemd notifications) protocol and will also tell systemd its current state (Running or Stopped)
when it changes.
The freqtrade.service.watchdog file contains an example of the service unit configuration file which uses systemd
as the watchdog.
!!! Note The sd_notify communication between the bot and the systemd service manager will not work if the bot runs in a Docker container.