update
This commit is contained in:
@@ -124,3 +124,28 @@ maintenance evacuation routing, HA affinity parsing, host-profile migration
|
||||
signatures and backups, and VirtIO filename validation. Tests use temporary
|
||||
files and mocked Proxmox output; they do not download installers or change a
|
||||
Proxmox host.
|
||||
## Deployment broker URL
|
||||
|
||||
TA-ProxMenu exchanges deployment codes with the configured TAPM broker. The
|
||||
URL is selected in this order:
|
||||
|
||||
1. Existing `TAPM_BROKER_URL` environment variable
|
||||
2. `TAPM_BROKER_URL` in `/etc/ta-proxmenu/config.env`
|
||||
|
||||
For a persistent per-system setting:
|
||||
|
||||
```sh
|
||||
install -d -m 0755 /etc/ta-proxmenu
|
||||
install -m 0644 config.env.example /etc/ta-proxmenu/config.env
|
||||
```
|
||||
|
||||
The tracked example contains only:
|
||||
|
||||
```dotenv
|
||||
TAPM_BROKER_URL=https://tapm.example.com
|
||||
```
|
||||
|
||||
Replace it with the deployed HTTPS origin, without an API path. There is no
|
||||
hard-coded operational broker URL; authorization fails with a configuration
|
||||
message when the variable is missing or invalid. Repository updates do not
|
||||
overwrite the system configuration file.
|
||||
|
||||
Reference in New Issue
Block a user