English: docs/en/linux.md | 中文: docs/zh/linux.md
This page only covers Linux-specific differences. For the shared setup flow, see Getting Started.
Download from Releases:
clipal-linux-amd64clipal-linux-arm64
Example:
chmod +x ./clipal-linux-amd64
sudo mv ./clipal-linux-amd64 /usr/local/bin/clipal
clipal --versionFor a quick short-lived background run:
nohup clipal >/dev/null 2>&1 &Useful for short-term use, but not the preferred long-running setup.
The recommended approach is the built-in command flow:
clipal service install
clipal service status
clipal service restart
clipal service stop
clipal service uninstallUseful variants:
clipal service install --force
clipal service install --config-dir /path/to/configIf you want to manage the unit file yourself, create:
~/.config/systemd/user/clipal.service
Minimal example:
[Unit]
Description=clipal local proxy
After=network.target
[Service]
Type=simple
ExecStart=/usr/local/bin/clipal --config-dir %h/.clipal
Restart=always
RestartSec=2
[Install]
WantedBy=default.targetEnable and start it:
systemctl --user daemon-reload
systemctl --user enable --now clipal.serviceFor long-running setups, this is a good default in config.yaml:
log_stdout: false
log_retention_days: 7Two common log sources:
- Clipal's own rotating logs
journalctl --user -u clipal.service -e
- If the port is in use, change
portor override with--port - If the binary lives under your home directory, update
ExecStartaccordingly
For shared issues, continue with Troubleshooting.