-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy path.env-sample
More file actions
73 lines (51 loc) · 2.74 KB
/
.env-sample
File metadata and controls
73 lines (51 loc) · 2.74 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
## Your OpenAI API key (required)
OPENAI_API_KEY='your-openai-api-key'
## Neo4j Graph DB credentials (optional for memory, see README)
# NEO4J_URI=
# NEO4J_USER=neo4j
# NEO4J_PASSWORD=your-password
## By default, the Worker and Client will connect to a local Temporal server (127.0.0.1:7233),
## on namespace 'default'. This is fine for development purposes and local testing.
##
## To use Temporal Cloud instead, uncomment the following:
# TEMPORAL_PROFILE='cloud'
## And follow instructions in the README for running demo on Temporal Cloud.
## Alternately, configure these variables.
# TEMPORAL_PROFILE='default'
# TEMPORAL_ADDRESS='127.0.0.1:7233'
# TEMPORAL_NAMESPACE='default'
# TEMPORAL_API_KEY=''
## The task queue to use for the worker
# TEMPORAL_TASK_QUEUE='research-queue'
## The Triage agent is responsible for deciding whether claryfing questions are needed, or
## if the initial query was already specific enough. This is nice in a real world scenario, but
## ain't great for demo purposes, where we _do_ want to show the clarifying agent in action.
## Setting this option to 'Y' will force the triage agent to ALWAYS ask for clarifying questions.
BYPASS_TRIAGE_AGENT='Y'
## Neo4j Memory Configuration (optional)
## Neo4j is used to persist conversation/workflow history, allowing users to
## resume previous conversations after page reloads.
##
## If not configured, the app will work without memory features (conversations
## won't be saved or resumable).
# NEO4J_URI='bolt://localhost:7687'
# NEO4J_USER='neo4j'
# NEO4J_PASSWORD='your-neo4j-password'
## Redpanda Event Streaming Configuration (optional)
## Configure these values for your Redpanda instance (local, cloud, or serverless).
## Multiple bootstrap servers can be specified as comma-separated values.
## Topics can be configured per event type for fine-grained streaming control.
## Connection Settings
# REDPANDA_BOOTSTRAP_SERVERS='localhost:9092' # Comma-separated list of brokers
## Topic Configuration
## Use a single topic for all events or separate topics per event category
# REDPANDA_TOPIC='research-workflow-events' # Default topic for all events
# REDPANDA_TOPIC_LIFECYCLE='workflow-lifecycle' # query_received, research_complete, etc.
# REDPANDA_TOPIC_CLARIFICATIONS='workflow-clarifications' # clarification events
# REDPANDA_TOPIC_RESEARCH='workflow-research' # research pipeline events
# REDPANDA_TOPIC_ARTIFACTS='workflow-artifacts' # image_generated, pdf_generated, etc.
## Security Configuration (required for Redpanda Serverless/Cloud)
# REDPANDA_SASL_MECHANISM='SCRAM-SHA-256' # Options: SCRAM-SHA-256, SCRAM-SHA-512, PLAIN
# REDPANDA_SASL_USERNAME='your-username'
# REDPANDA_SASL_PASSWORD='your-password'
# REDPANDA_SECURITY_PROTOCOL='SASL_SSL' # Options: PLAINTEXT, SASL_SSL, SSL