From 3d46bed09fb39cbb26cfb68454fea17ca4822b15 Mon Sep 17 00:00:00 2001 From: Dylan Audius Date: Thu, 21 May 2026 10:13:52 -0700 Subject: [PATCH] staking: pass solana_rpc_endpoint and eth_rpc_endpoint via env The staking pedalboard service reads `process.env.solana_rpc_endpoint` and `process.env.eth_rpc_endpoint` at boot, but the compose entry never forwarded them. Add `env_file: .env` plus an explicit `environment:` block (matching the pattern other pedalboard services use) so the service actually has its RPC URLs in prod. Co-Authored-By: Claude Opus 4.7 (1M context) --- dev-tools/compose/docker-compose.pedalboard.prod.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/dev-tools/compose/docker-compose.pedalboard.prod.yml b/dev-tools/compose/docker-compose.pedalboard.prod.yml index 172eaf1e569..94bcb0885df 100644 --- a/dev-tools/compose/docker-compose.pedalboard.prod.yml +++ b/dev-tools/compose/docker-compose.pedalboard.prod.yml @@ -41,6 +41,10 @@ services: app_name: staking TURBO_TEAM: '${TURBO_TEAM}' TURBO_TOKEN: '${TURBO_TOKEN}' + env_file: .env + environment: + solana_rpc_endpoint: '${SOLANA_RPC_ENDPOINT}' + eth_rpc_endpoint: '${ETH_RPC_ENDPOINT}' restart: always profiles: - pedalboard