kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-14 13:05:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(services): route a service remote from services.<TAG>.dl.remote

Browse Source 
Click picks the subcommand before the dl callback applies the service config, so Services.resolve_command now applies remote and server first. A REST API job routes from its request only.
This commit is contained in:
imSp4rky
2026-10-19 14:19:07 -06:00
parent 4728ac593c
commit 3aaf9c4107
8 changed files with 208 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dev/rest-api/remote-sessions.md
+21 -2
View File
@@ -87,18 +87,37 @@ remote_services:
If you configure exactly one server, unshackle uses it implicitly:
```bash
unshackle dl EXAMPLE 0ABCDEF
unshackle dl --remote EXAMPLE 0ABCDEF
```
If you configure **more than one** server, you must pick one with `--server`:
```bash
unshackle dl --server my_server EXAMPLE 0ABCDEF
unshackle dl --remote --server my_server EXAMPLE 0ABCDEF
```
With no `remote_services` configured at all, unshackle raises a clear error telling
you to add the block shown above.
### Making a service remote by default
To run a service on the server without `--remote`, set `remote` in the
[`services`](../../reference/configuration/services.md#services) block, not in the
`services` sub-dict of `remote_services`. Add `server` to select one of several servers:
```yaml title="unshackle.yaml (client)"
services:
EXAMPLE:
dl:
remote: true
server: my_server
```
`unshackle dl EXAMPLE 0ABCDEF` and `unshackle search EXAMPLE "query"` then run on
`my_server`. A `--server` on the command line overrides the configured server. The global
`dl: remote: true` makes every `dl` run remote, but it has no effect on `search`.
The REST API ignores both settings: a job runs remote only when its request asks for it.
---
## What happens during a download