Repository navigation
Expand file tree
/
Copy pathprivate.env.example
More file actions
74 lines (60 loc) · 3.43 KB
/
Copy pathprivate.env.example
File metadata and controls
74 lines (60 loc) · 3.43 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
# ==============================================================================
# AXIONOS BUILD SYSTEM - LOCAL CONFIGURATION
# ==============================================================================
# Copy this file to "telegram-bot/private.env" and fill in your details.
# This file governs the local Telegram Bot service running on your server.
# Do NOT commit your active "private.env" file to Git!
# === TELEGRAM BOT CONFIGURATION ===
# Your Telegram Bot Token obtained from @BotFather (e.g., 123456789:ABCDef...)
BOT_TOKEN=123456789:ABCDefghIJKLmnopQRSTuvwxYZ
# The main channel or group ID for build status notifications (e.g., -100...)
CHANNEL_ID=-1001234567890
# Optional: Thread ID if your Telegram group has "Topics" (Forums) enabled.
# Leave blank or set to none if using a regular group or channel.
TOPIC_BUILDER=1
# Your personal Telegram User ID (used for owner-only administrative commands)
OWNER_ID=12345678
# === GITHUB INTEGRATION ===
# GitHub Personal Access Token (PAT) with "repo" scope (for triggering workflows & DB syncs)
GITHUB_TOKEN=ghp_your_secret_github_token_here
# Your GitHub Repository (e.g., "Owner/RepoName")
GITHUB_REPO_NAME=AxionOS/build_server
# The branch to use for CI/CD builds and database.json updates (default: "actions")
GITHUB_BRANCH=actions
# === DATABASE & REDIS ===
# Redis connection string (e.g., redis://localhost:6379/4)
REDIS_URL=redis://localhost:6379/4
# === PERMISSIONS & SYSTEM ACCESS ===
# Comma-separated list of authorized Telegram Chat/Group IDs that can trigger commands
ALLOWED_CHAT_IDS=-1001234567890,-1009876543210
# Comma-separated list of authorized Telegram User IDs granted administrator access
ADMIN_USER_IDS=12345678,87654321
# === TESTING CONFIGURATION ===
# Optional: Chat and Channel IDs used for bot developer testing
TEST_GROUP_ID=-1001111111111
TEST_CHANNEL_ID=-1002222222222
# === PIXELDRAIN STORAGE CONFIGURATION ===
# Optional: Pixeldrain API Key for authenticated uploads (found at https://pixeldrain.com/user/api_keys)
# If empty or not set, uploads will proceed anonymously (limited to 20GB).
PD_API_KEY=your_pixeldrain_api_key_here
# ==============================================================================
# GITHUB REPOSITORY SECRETS (SET ON GITHUB.COM)
# ==============================================================================
# The following credentials must NOT be in your local "private.env" file!
# Instead, add them on GitHub.com under: Settings -> Secrets and variables -> Actions
#
# 1. GITHUB ACTIONS ENVIRONMENT:
# - GH_PAT : Personal Access Token (same as GITHUB_TOKEN above)
# - TELEGRAM_TOKEN : Bot Token (same as BOT_TOKEN above)
# - TELEGRAM_CHAT_ID : Target chat ID (same as CHANNEL_ID above)
# - TOPIC_BUILDER : Thread ID (same as TOPIC_BUILDER above)
# - TOPIC_ERROR_LOGS : Thread ID for posting compile error logs
# - TOPIC_RELEASE_JSON: Thread ID for posting release JSON artifacts
#
# 2. CLOUDFLARE R2 BUCKET (OPTIONAL CDN UPLOAD ON SUCCESS):
# - R2_ACCESS_KEY : Cloudflare R2 Access Key ID
# - R2_SECRET_KEY : Cloudflare R2 Secret Access Key
# - R2_ACCOUNT_ID : Cloudflare R2 Account ID (found in Cloudflare Dashboard URL)
# - R2_BUCKET : Name of your Cloudflare R2 bucket (e.g., "axionos-releases")
# - R2_CDN_DOMAIN : Custom domain mapped to your bucket (e.g., "https://cdn.axionos.org")
# ==============================================================================