-
Notifications
You must be signed in to change notification settings - Fork 14
Expand file tree
/
Copy path.env.example
More file actions
23 lines (18 loc) · 1.21 KB
/
.env.example
File metadata and controls
23 lines (18 loc) · 1.21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# Example .env file for eval protocol development
# Copy this file to .env (in your project root) and fill in your actual values.
# IMPORTANT: Add .env to your .gitignore file to avoid committing secrets!
# Fireworks AI Credentials (for interacting with the Fireworks platform)
# These are used by eval protocol to deploy evaluators to Fireworks, preview, etc.
FIREWORKS_API_KEY="your_fireworks_api_key_here"
# Optional: If targeting a non-production Fireworks API endpoint
# FIREWORKS_API_BASE="https://dev.api.fireworks.ai"
# GCP Configuration (for --target gcp-cloud-run if not using eval-protocol.yaml or CLI args)
# Note: It's generally recommended to set these in eval-protocol.yaml or pass via CLI for specific projects.
# However, you can set global defaults here if you frequently work with the same GCP setup.
# GCP_PROJECT_ID="your_default_gcp_project_id"
# GCP_REGION="your_default_gcp_region" # e.g., us-central1
# GCP_AR_REPO="your_default_artifact_registry_repo_name" # e.g., eval-protocol-evaluators
# E2B API Key (if working with E2B code execution features)
# E2B_API_KEY="your_e2b_api_key_here"
# Other environment variables your custom reward functions might need
# MY_CUSTOM_SERVICE_API_KEY="some_other_key"