-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
141 lines (125 loc) · 6.07 KB
/
Copy path.env.example
File metadata and controls
141 lines (125 loc) · 6.07 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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
# manydns API Test Credentials
# Copy this file to `.env` and fill in your values
# The .env file is gitignored and safe for credentials
# =============================================================================
# DNSPOD PROVIDER (Legacy API)
# =============================================================================
# Uses the legacy DNSPod API at api.dnspod.com with simple token authentication.
#
# Console: https://console.dnspod.com/account/token/token
# Endpoint: api.dnspod.com
# Auth: Simple token format "{ID},{Token}" in POST body
# Feature: --features dnspod
# =============================================================================
# DNSPod API Token
# Generate at: https://console.dnspod.com/account/token/token
DNSPOD_TOKEN_ID=123456
DNSPOD_TOKEN=your_token_here
# User-Agent configuration (required by DNSPod API spec)
# <https://docs.dnspod.com/api/api-development/>
# These should identify YOUR program, not the library
DNSPOD_TEST_PROGRAM=my-test-app
DNSPOD_TEST_VERSION=1.0.0
DNSPOD_TEST_EMAIL=your@email.com
# Test Domain Configuration for DNSPod
# FQDN of a domain you control for running integration tests
# WARNING: Tests will create/modify/delete records in this domain!
DNSPOD_TEST_DOMAIN=example.com
# Subdomain prefix for test records (e.g., "dnspod-api-test" creates dnspod-api-test.example.com)
DNSPOD_TEST_SUBDOMAIN=dnspod-api-test
# =============================================================================
# TENCENT CLOUD PROVIDER (Modern API)
# =============================================================================
# Uses the Tencent Cloud API at dnspod.intl.tencentcloudapi.com with
# TC3-HMAC-SHA256 signature authentication.
#
# Console: https://console.tencentcloud.com/capi
# Endpoint: dnspod.intl.tencentcloudapi.com
# Auth: TC3-HMAC-SHA256 signature in headers
# Feature: --features tencent
# =============================================================================
# Tencent Cloud API Keys
# Generate at: https://console.tencentcloud.com/capi
TENCENT_SECRET_ID=your_secret_id_here
TENCENT_SECRET_KEY=your_secret_key_here
# Test Domain Configuration for Tencent
# FQDN of a domain you control for running integration tests
# WARNING: Tests will create/modify/delete records in this domain!
TENCENT_TEST_DOMAIN=example.com
# Subdomain prefix for test records (e.g., "tencent-api-test" creates tencent-api-test.example.com)
TENCENT_TEST_SUBDOMAIN=tencent-api-test
# =============================================================================
# CLOUDFLARE PROVIDER
# =============================================================================
# Uses the Cloudflare API at api.cloudflare.com/client/v4 with Bearer token
# authentication.
#
# Console: https://dash.cloudflare.com/profile/api-tokens
# Endpoint: api.cloudflare.com/client/v4
# Auth: Bearer token in Authorization header
# Feature: --features cloudflare
# =============================================================================
# Cloudflare API Token
# Generate at: https://dash.cloudflare.com/profile/api-tokens
# Token needs Zone:Read and DNS:Edit permissions
CLOUDFLARE_API_TOKEN=your_api_token_here
# Test Domain Configuration for Cloudflare
# FQDN of a domain you control for running integration tests
# WARNING: Tests will create/modify/delete records in this domain!
CLOUDFLARE_TEST_DOMAIN=example.com
# Subdomain prefix for test records (e.g., "cloudflare-api-test" creates cloudflare-api-test.example.com)
CLOUDFLARE_TEST_SUBDOMAIN=cloudflare-api-test
# =============================================================================
# NAMECHEAP PROVIDER
# =============================================================================
# Uses the Namecheap API with XML responses. Supports both sandbox and
# production environments.
#
# Dashboard: https://ap.www.namecheap.com/settings/tools/apiaccess/
# Sandbox: https://ap.www.sandbox.namecheap.com/settings/tools/apiaccess/
# Production Endpoint: api.namecheap.com/xml.response
# Sandbox Endpoint: api.sandbox.namecheap.com/xml.response
# Auth: API user/key + whitelisted client IP
# Feature: --features namecheap
#
# IMPORTANT: You must whitelist your client IP in the Namecheap dashboard!
# =============================================================================
# Namecheap API Credentials
# For production: https://ap.www.namecheap.com/settings/tools/apiaccess/
# For sandbox: https://ap.www.sandbox.namecheap.com/settings/tools/apiaccess/
NAMECHEAP_API_USER=your_username
NAMECHEAP_API_KEY=your_api_key
# Your public IP address (must be whitelisted in Namecheap dashboard)
NAMECHEAP_CLIENT_IP=1.2.3.4
# Environment: "sandbox" or "production"
NAMECHEAP_ENVIRONMENT=sandbox
# Test Domain Configuration for Namecheap
# FQDN of a domain you control for running integration tests
# WARNING: Tests will create/modify/delete records in this domain!
NAMECHEAP_TEST_DOMAIN=example.com
# Subdomain prefix for test records (e.g., "namecheap-api-test" creates namecheap-api-test.example.com)
NAMECHEAP_TEST_SUBDOMAIN=namecheap-api-test
# =============================================================================
# HETZNER DNS PROVIDER
# =============================================================================
# Uses the Hetzner DNS API at dns.hetzner.com/api/v1 with API token
# authentication.
#
# Console: https://console.hetzner.com/projects/YOUR_PROJECT_ID/security/tokens
# Endpoint: dns.hetzner.com/api/v1
# Auth: Auth-API-Token header
# Feature: --features hetzner
#
# UNIQUE FEATURES:
# - Supports zone creation/deletion via API (CreateZone, DeleteZone traits)
# - Zone status tracking (Verified, Pending, Failed)
# =============================================================================
# Hetzner DNS API Token
# Generate at: https://console.hetzner.com/projects/YOUR_PROJECT_ID/security/tokens
HETZNER_API_TOKEN=your_api_token_here
# Test Domain Configuration for Hetzner
# FQDN of a domain you control for running integration tests
# WARNING: Tests will create/modify/delete records in this domain!
HETZNER_TEST_DOMAIN=example.com
# Subdomain prefix for test records (e.g., "hetzner-api-test" creates hetzner-api-test.example.com)
HETZNER_TEST_SUBDOMAIN=hetzner-api-test