-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathconfig.sample.yaml
More file actions
31 lines (24 loc) · 1.24 KB
/
Copy pathconfig.sample.yaml
File metadata and controls
31 lines (24 loc) · 1.24 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
# Aspera Node API Configuration
# Copy this file to config.yaml and fill in your settings.
# Aspera Node server URL (e.g., https://node.example.com:9092)
# This replaces the separate `host` and `port` settings.
# Port is optional: defaults to 80 for http, 443 for https.
url: "https://node.example.com:9092"
user: "node_user"
password: "your_password"
# SSL verification (set to false for self-signed certificates)
verify_ssl: true
# Request timeout in seconds (default: 30)
timeout: 30
# Gen4 API support (set to false to disable Accept-Version: 4.0 features)
accept_v4: true
# Optional: RSA private key for dynamic key authentication.
# When set, the public key is sent in download_setup request and
# the private key is passed to ascp via ASPERA_SCP_SSH_PRIVATE_KEY env var.
# private_key_file: "/path/to/aspera_private_key.pem"
# Before using download commands, run: aspera setup
# This installs the Aspera Connect SDK and generates:
# - Bypass key: ~/.aspera/connect/client/aspera_bypass_rsa.pem (token auth)
# - Fallback key: ~/.aspera/connect/client/aspera_fallback_cert_private_key.pem (HTTP fallback)
# - Fallback cert: ~/.aspera/connect/client/aspera_fallback_cert.pem (HTTP fallback)
# These keys are automatically applied to download commands.