-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
131 lines (108 loc) · 5.64 KB
/
Copy path.env.example
File metadata and controls
131 lines (108 loc) · 5.64 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
# OpenClaw 6-Agent System Environment Configuration
# Copy this file to .env and fill in your actual values
# DO NOT commit .env to version control - it contains secrets!
# =============================================================================
# NEO4J CONFIGURATION
# =============================================================================
# Neo4j connection settings for the knowledge graph
# Used by all agents for memory storage and retrieval
# Neo4j Bolt URI - use bolt://neo4j:7687 for internal Docker network
# or the external URL provided by your Neo4j host (e.g., Neo4j Aura)
NEO4J_URI=bolt://neo4j:7687
# Neo4j username (default is usually 'neo4j')
NEO4J_USER=neo4j
# Neo4j password - CHANGE THIS to your actual Neo4j password
# Must be a strong password, especially for production deployments
NEO4J_PASSWORD=CHANGE_THIS_TO_YOUR_NEO4J_PASSWORD
# Neo4j database name (default: neo4j)
# Only change if using a specific named database in Neo4j 4.0+
NEO4J_DATABASE=neo4j
# =============================================================================
# OPENCLAW GATEWAY CONFIGURATION
# =============================================================================
# Settings for the OpenClaw gateway that handles agent communication
# and webhook processing
# URL of the OpenClaw gateway
# For Railway deployment: https://your-service.railway.app
# For local development: http://localhost:3000
OPENCLAW_GATEWAY_URL=https://kublai.kurult.ai
# Secure authentication token for gateway access
# Generate with: openssl rand -hex 32
# CHANGE THIS to a secure random token (64 hex characters recommended)
OPENCLAW_GATEWAY_TOKEN=CHANGE_THIS_TO_A_SECURE_RANDOM_TOKEN_32_CHARS_MIN
# =============================================================================
# SIGNAL MESSENGER CONFIGURATION
# =============================================================================
# Signal integration for admin notifications and group management
# Requires signal-cli to be installed and configured
# Signal account phone number (E.164 format: +1234567890)
# This is the number that will send/receive Signal messages
SIGNAL_ACCOUNT_NUMBER=+1234567890
# Path to the signal-cli binary
# Default locations:
# macOS (Homebrew): /opt/homebrew/bin/signal-cli
# Linux: /usr/bin/signal-cli
# Docker: /usr/local/bin/signal-cli
SIGNAL_CLI_PATH=/opt/homebrew/bin/signal-cli
# Primary admin phone number for notifications (E.164 format)
# This person receives critical alerts and can send admin commands
ADMIN_PHONE_1=+1234567890
# Secondary admin phone number for group notifications (E.164 format)
# Used for group chat where both admins should be present
ADMIN_PHONE_2=+1234567890
# =============================================================================
# AGENT AUTHENTICATION
# =============================================================================
# Shared secret for agent-to-agent authentication
# Ensures only authorized agents can communicate with each other
# Agent authentication secret
# Generate with: openssl rand -hex 32
# CHANGE THIS to a secure random secret (64 hex characters recommended)
# All agents must use the same secret to authenticate with each other
AGENT_AUTH_SECRET=CHANGE_THIS_TO_A_SECURE_32_CHAR_MINIMUM_SECRET
# =============================================================================
# OPTIONAL INTEGRATIONS
# =============================================================================
# Uncomment and configure the integrations you want to enable
# -----------------------------------------------------------------------------
# Notion Integration (Phase 8)
# -----------------------------------------------------------------------------
# NOTION_API_TOKEN=secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# NOTION_DATABASE_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
# -----------------------------------------------------------------------------
# ClawTasks Blockchain Integration (Phase 5)
# -----------------------------------------------------------------------------
# Base network RPC URL for blockchain interactions
# BASE_RPC_URL=https://mainnet.base.org
# -----------------------------------------------------------------------------
# LLM Integration
# -----------------------------------------------------------------------------
# Moonshot API key for agent LLM capabilities
# Get your API key from: https://platform.moonshot.cn/
# MOONSHOT_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# =============================================================================
# MONITORING & LOGGING
# =============================================================================
# Observability settings for debugging and production monitoring
# Log level for all agents
# Options: debug, info, warn, error
# - debug: Verbose logging for development
# - info: Standard operational logging (recommended for production)
# - warn: Only warnings and errors
# - error: Critical errors only
LOG_LEVEL=info
# Prometheus metrics port
# Agents expose metrics on this port for scraping by Prometheus
# Default: 9090
PROMETHEUS_PORT=9090
# =============================================================================
# SECURITY NOTES
# =============================================================================
# 1. NEVER commit .env files to version control
# 2. Use strong, unique passwords for all services
# 3. Rotate secrets regularly (recommended: every 90 days)
# 4. Use environment-specific .env files (e.g., .env.production)
# 5. Store production secrets in a secure vault (e.g., Railway variables,
# AWS Secrets Manager, HashiCorp Vault)
# 6. Keep signal-cli registration separate from this configuration
# =============================================================================