Configuration and files
Where Cloud-PBS TUI stores its configuration and logs, and how the token is protected.
Last updated: May 18, 2026
Cloud-PBS TUI stores its configuration locally, on the host. No data is sent anywhere other than to the PBS server you have configured.
File locations
The tool follows the XDG Base Directory specification:
| Content | Default location |
|---|---|
| Configuration | ~/.config/cloudpbs-tui/ |
| Logs and runtime data | ~/.local/state/cloudpbs-tui/ |
These locations honour the XDG_CONFIG_HOME and XDG_STATE_HOME environment variables when they are set.
Automatic saving
The configuration (target, sources, schedule, interface language) is saved:
- on every screen change;
- when the application closes (
qorCtrl+C).
From one session to the next, you therefore find your configuration again without having to re-enter it.
The API token
The API token secret is treated as sensitive data: it is masked as you type in the Target screen. It is nonetheless stored in the configuration file so that scheduled backups can run unattended. Make sure the ~/.config/cloudpbs-tui/ directory is readable only by the relevant user.
The encryption key
The encryption key file is not managed by Cloud-PBS TUI: its path is free and it is up to you to choose and protect it. See Encryption.
Scheduling
The systemd units generated by the Schedule screen are not stored in the configuration directory: they are placed where systemd expects them, according to the chosen installation level (user or system).