-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
115 lines (92 loc) · 4.57 KB
/
.env.example
File metadata and controls
115 lines (92 loc) · 4.57 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
# Fast Agent Docker Environment Configuration
# ====================================================================
# GOOGLE API CONFIGURATION (Required for fast-agent)
# ====================================================================
# Your Google Gemini API key (get from: https://aistudio.google.com/app/apikey)
GOOGLE_API_KEY=
# ====================================================================
# GENERIC BASE URL (Required for fast-agent)
# ====================================================================
# Your generic base URL (e.g., http://localhost:8080/gigachat-adapter/v1)
GENERIC_BASE_URL=
# ====================================================================
# BITBUCKET SERVER CONFIGURATION (Required for pull requests)
# ====================================================================
# Your Bitbucket Server URL (e.g., https://bitbucket.your-company.com)
BITBUCKET_URL=
# Bitbucket Personal Access Token (create in your Bitbucket Server user settings)
BITBUCKET_TOKEN=
# The Bitbucket workspace/project to work with
BITBUCKET_WORKSPACE=
# ====================================================================
# BITBUCKET CONTAINER CONFIGURATION (For running Bitbucket locally)
# ====================================================================
# One-time setup token for initial Bitbucket configuration
BITBUCKET_SETUP_TOKEN=
# Display name for the Bitbucket server instance
BITBUCKET_SETUP_DISPLAYNAME=Bitbucket
# Admin email for Bitbucket setup
BITBUCKET_SETUP_EMAIL=admin@example.com
# ====================================================================
# JIRA CONFIGURATION (Required for ticket reading)
# ====================================================================
# Your JIRA instance URL (e.g., https://your-domain.atlassian.net for Cloud)
JIRA_URL=
# Your JIRA username/email
JIRA_USERNAME=
# JIRA API Token (create at: https://id.atlassian.com/manage-profile/security/api-tokens)
JIRA_TOKEN=
# ====================================================================
# CONFLUENCE CONFIGURATION (Optional - part of Atlassian suite)
# ====================================================================
# Your Confluence instance URL (usually same as JIRA if same instance)
CONFLUENCE_URL=
# Your Confluence username/email (usually same as JIRA)
CONFLUENCE_USERNAME=
# Confluence API Token (usually same as JIRA if same instance)
CONFLUENCE_TOKEN=
# ====================================================================
# SSH KEY CONFIGURATION (Optional - for git SSH operations)
# ====================================================================
# Git user name (for commits when using SSH keys)
GIT_USER_NAME=Docker User
# Git user email (for commits when using SSH keys)
GIT_USER_EMAIL=docker@example.com
# SSH Key Path (optional - leave empty if using default ~/.ssh directory)
# SSH_KEY_PATH=
# ====================================================================
# EXAMPLE CONFIGURATIONS
# ====================================================================
# Cloud Examples:
# JIRA_URL=https://mycompany.atlassian.net
# BITBUCKET_WORKSPACE=mycompany
# Server Examples:
# JIRA_URL=https://jira.mycompany.com
# Bitbucket Server would use different configuration (contact admin)
# ====================================================================
# GPT 2 GIGA Fast Agent Configuration
# ====================================================================
# Credentials for GigaChat API (get from: https://gigachat.devices.sberbank.ru/api/v1/credentials)
GIGACHAT_CREDENTIALS=
# Base URL for GigaChat API (get from: https://gigachat.devices.sberbank.ru/api/v1/credentials)
GIGACHAT_BASE_URL=https://gigachat.devices.sberbank.ru/api/v1
# Client ID for GigaChat API (get from: https://gigachat.devices.sberbank.ru/api/v1/credentials)
GIGACHAT_SCOPE=GIGACHAT_API_CORP
# Model for GigaChat API (get from: https://gigachat.devices.sberbank.ru/api/v1/models)
GIGACHAT_MODEL=GigaChat
# Verify SSL certificates when connecting to GigaChat API (optional)
GIGACHAT_VERIFY_SSL_CERTS=
# ====================================================================
# INSTRUCTIONS
# ====================================================================
# 1. Copy this file to .env: cp .env.example .env
# 2. Fill in your actual credentials
#
# SSH Setup (Optional):
# If you want to use SSH keys for git operations:
# - Place your SSH keys in ~/.ssh/ (id_rsa, id_rsa.pub, id_ed25519, etc.)
# - Or set SSH_KEY_PATH to specify a custom SSH key directory
# - Fill in GIT_USER_NAME and GIT_USER_EMAIL for commits
#
# 3. Run: docker-compose up
# 4. The container will have access to MCP tools for Bitbucket, JIRA, and git