I have installed Jackett using the standard dietpi-software , and have noticed some concerns.
I am using bookworm (PI4) with the current DietPi v9.0.2.
After install I noticed the service is run with:
[Unit]
Description=Jackett (DietPi)
Wants=network-online.target
After=network-online.target
StartLimitIntervalSec=60
StartLimitBurst=5
[Service]
SyslogIdentifier=Jackett
User=jackett
WorkingDirectory=/opt/jackett
Environment=XDG_CONFIG_HOME=/opt/jackett
ExecStart=/bin/dash -c '/opt/jackett/jackett --NoRestart; ec=$?; while pgrep -u jackett JackettUpdater /dev/null; do sleep 1; done; exit $ec'
Restart=always
RestartSec=5
# Hardening
ProtectSystem=strict
ProtectHome=true
PrivateDevices=true
PrivateTmp=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectControlGroups=true
NoNewPrivileges=true
ReadWritePaths=-/opt/jackett
[Install]
WantedBy=multi-user.target
This to me implies the config files are stored within the jackett runtime directory as well (ie /opt/jackett/).
This doesn’t seem to conform with the practice of utilizing the /mnt/dietpi_userdata/ dir or for that matter even segmenting and separating the custom config files into a ~/.config/ folder (if running as a user).
Was there a reason to have the Jackett config files stored in the same folder as the Jackett folder itself (by default dietpi-software install) ?
I can manually change these, but wanted to know if there was a reason why it was done that way first.
/opt/jackett/ folder contains all the jackett files needed to run Jackett but by default dietpi-software appears to install all Jackett files (configs, custom settings, etc.) as well.
The subfolders in /opt/jackett/
drwxr-xr-x 7 jackett jackett 4096 Content/ <-- web content (part of Jackett)
drwxr-xr-x 2 jackett jackett 20480 Definitions/ <-- *.yml files for trackers (url's, any API keys, etc.)
drwxr-xr-x 4 jackett jackett 4096 Jackett/ <-- Jackett Config files
I presume /opt/jackett/Definitions/ and /opt/jackett/Jackett/ subfolders are the only locations for custom config/settings. etc. so I can move them and re-configure the service (in /etc/systemd/*). Will future updates over-ride these?