terminal/.env.example at main · withObsrvr/terminal · GitHub

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
# ============================================================================
# MULTI-NETWORK CONFIGURATION
# ============================================================================
# The application supports both Mainnet and Testnet data sources.
# Configure connection details for each network below.

# Default network on startup (mainnet or testnet)
DEFAULT_NETWORK=testnet

# ============================================================================
# MAINNET CONFIGURATION
# ============================================================================

# PostgreSQL connection for Mainnet hot data (recent 6 months)
POSTGRES_URL_MAINNET=postgres://user:password@localhost/obsrvr_mainnet?sslmode=disable

# DuckLake catalog for Mainnet cold data (OPTIONAL - for lakehouse integration)
# Path to DuckLake catalog (PostgreSQL-backed)
# Format: ducklake:postgres:postgresql:///DATABASE_NAME?host=/path/to/.postgres-sockets
DUCKLAKE_CATALOG_PATH_MAINNET=ducklake:postgres:postgresql:///ducklake_obsrvr_mainnet?host=/home/user/.postgres-sockets

# Catalog name for Mainnet (the AS name when attaching, e.g., "obsrvr_mainnet_1")
DUCKLAKE_CATALOG_NAME_MAINNET=obsrvr_mainnet_1

# Schema name for Mainnet within the catalog (e.g., "mainnet")
DUCKLAKE_SCHEMA_NAME_MAINNET=mainnet

# Path to DuckLake Parquet data directory for Mainnet (ABSOLUTE PATH REQUIRED)
# Example: If ingestion runs from /home/user/ducklake-ingestion-obsrvr with data_path "./obsrvr_mainnet_1"
# then set: DUCKLAKE_DATA_PATH_MAINNET=/home/user/ducklake-ingestion-obsrvr/obsrvr_mainnet_1
DUCKLAKE_DATA_PATH_MAINNET=/path/to/ducklake-ingestion-obsrvr/obsrvr_mainnet_1

# ============================================================================
# TESTNET CONFIGURATION
# ============================================================================

# PostgreSQL connection for Testnet hot data (recent 6 months)
POSTGRES_URL_TESTNET=postgres://user:password@localhost/obsrvr_testnet?sslmode=disable

# DuckLake catalog for Testnet cold data (OPTIONAL - for lakehouse integration)
# Path to DuckLake catalog (PostgreSQL-backed)
# Format: ducklake:postgres:postgresql:///DATABASE_NAME?host=/path/to/.postgres-sockets
DUCKLAKE_CATALOG_PATH_TESTNET=ducklake:postgres:postgresql:///ducklake_obsrvr_test_3?host=/home/user/.postgres-sockets

# Catalog name for Testnet (the AS name when attaching, e.g., "obsrvr_test_3")
DUCKLAKE_CATALOG_NAME_TESTNET=obsrvr_test_3

# Schema name for Testnet within the catalog (e.g., "testnet")
DUCKLAKE_SCHEMA_NAME_TESTNET=testnet

# Path to DuckLake Parquet data directory for Testnet (ABSOLUTE PATH REQUIRED)
DUCKLAKE_DATA_PATH_TESTNET=/path/to/ducklake-ingestion-obsrvr/obsrvr_test_data_3

# ============================================================================
# LEGACY SINGLE-NETWORK CONFIGURATION (DEPRECATED)
# ============================================================================
# These variables are kept for backward compatibility but are no longer used
# when multi-network configuration is present. Use the network-specific
# variables above instead.

# DuckDB path for cold data queries (local file, used as fallback)
DUCKDB_PATH=./data/obsrvr_cold.duckdb

# ============================================================================
# SHARED CONFIGURATION
# ============================================================================

# S3 configuration for parquet files (shared across networks)
S3_BUCKET=obsrvr-historical-data
S3_REGION=us-east-1
AWS_ACCESS_KEY_ID=your-access-key
AWS_SECRET_ACCESS_KEY=your-secret-key

# Application configuration
HOT_DATA_MONTHS=6
PORT=8081

# ============================================================================
# DuckLake Catalog Integration (OPTIONAL)
# ============================================================================
# Connect to an external DuckLake catalog (e.g., ducklake-ingestion-obsrvr)
# Uncomment and configure these to use a lakehouse as your cold storage:

# Path to DuckLake catalog (PostgreSQL-backed)
# Format: ducklake:postgres:postgresql:///DATABASE_NAME?host=/path/to/.postgres-sockets
# DUCKLAKE_CATALOG_PATH=ducklake:postgres:postgresql:///ducklake_obsrvr_test_3?host=/home/user/.postgres-sockets

# Catalog name (the AS name when attaching, e.g., "obsrvr_test_3")
# This should match the catalog_name in your ducklake-ingestion-obsrvr config
# DUCKLAKE_CATALOG_NAME=obsrvr_test_3

# Schema name within the catalog (e.g., "core")
# This should match the schema_name in your ducklake-ingestion-obsrvr config
# DUCKLAKE_SCHEMA_NAME=core

# Path to DuckLake Parquet data directory (ABSOLUTE PATH REQUIRED)
# IMPORTANT: If the catalog was created with a relative path (e.g., "./obsrvr_test_data_3"),
# you must provide the absolute path here. The application sets DuckDB's file_search_path
# to help resolve the relative paths stored in the catalog metadata.
# Example: If ingestion runs from /home/user/ducklake-ingestion-obsrvr with data_path "./obsrvr_test_data_3"
# then set: DUCKLAKE_DATA_PATH=/home/user/ducklake-ingestion-obsrvr/obsrvr_test_data_3
# DUCKLAKE_DATA_PATH=/path/to/ducklake-ingestion-obsrvr/obsrvr_test_data_3