dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

SearXNG deploy: do not enable the generated .network unit

Browse Source 
The quadlet .network unit is generator-managed and cannot be enabled; it is
pulled in automatically by the containers that set Wants=/After=searxng-network.
Enable only the three container units. The explicit start of the network is kept
(start works on generated units).
This commit is contained in:
Frank
2026-08-18 23:46:35 -07:00
parent f488382b08
commit d7c66b0253
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/deploy-searxng-quadlet.sh
+4 -2
View File
@@ -77,9 +77,11 @@ echo ' Copying quadlet units into ~/.config/containers/systemd/ ...'
mkdir -p ~/.config/containers/systemd
cp ${QDIR}/*.container ${QDIR}/*.network ~/.config/containers/systemd/
echo ' daemon-reload + enable for boot...'
echo ' daemon-reload + enable the container units for boot...'
# The .network unit is generator-managed: it cannot be enabled, and it is pulled
# in automatically by the containers that set Wants=/After=searxng-network.service.
systemctl --user daemon-reload
systemctl --user enable searxng-network.service gluetun.service searxng-valkey.service searxng.service
systemctl --user enable gluetun.service searxng-valkey.service searxng.service
echo ' Starting in dependency order...'
systemctl --user start searxng-network.service