-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathenv.example
More file actions
59 lines (53 loc) · 2.37 KB
/
env.example
File metadata and controls
59 lines (53 loc) · 2.37 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
# Ghost Server Configuration (SSE-first)
#
# GitHub credentials are provided by the MCP client via headers.
# Jira is handled by an external Atlassian MCP - configure it separately.
# This file is optional and only used for server-side database settings.
# ===========================================
# Database Configuration (activity tracking & reports)
# ===========================================
# Option 1: SQLite (default - no configuration needed)
# Just set the data directory where the SQLite file will be stored
GHOST_DATA_DIR=./data
# Option 2: PostgreSQL (for production deployments)
# Uncomment and configure the DATABASE_URL to use PostgreSQL
# DATABASE_URL=postgresql://user:password@localhost:5432/ghost
# ===========================================
# PostgreSQL Settings (only if using docker-compose with postgres profile)
# ===========================================
# POSTGRES_USER=ghost
# POSTGRES_PASSWORD=changeme
# POSTGRES_DB=ghost
# ===========================================
# Management Report Instructions (optional)
# ===========================================
# Path to a custom file containing management report generation instructions.
# The agent will read these instructions before generating reports.
# If not set, default instructions are used.
#
# Create your own by copying management_report_instructions.md.example
# MANAGEMENT_REPORT_INSTRUCTIONS_FILE=./management_report_instructions.md
# ===========================================
# GitHub Multi-Token Configuration (MCP client headers)
# ===========================================
# GitHub tokens are sent by the MCP client via HTTP headers, NOT stored server-side.
#
# Single token (simple):
# Set the X-GitHub-Token header in your MCP client config.
#
# Multiple tokens (for different orgs/repos):
# Set the X-GitHub-Tokens header with a JSON array of token-to-pattern mappings.
# Patterns use fnmatch-style globs matched against "owner/repo".
# First match wins. Use "*" as a catch-all fallback.
#
# Example MCP client configuration (e.g., in mcp.json):
# {
# "mcpServers": {
# "github": {
# "url": "http://localhost:8080/mcp/github",
# "headers": {
# "X-GitHub-Tokens": "[{\"token\":\"ghp_personal\",\"patterns\":[\"myuser/*\"]},{\"token\":\"ghp_org\",\"patterns\":[\"my-org/*\"]},{\"token\":\"ghp_fallback\",\"patterns\":[\"*\"]}]"
# }
# }
# }
# }