From 050e10e2849166aef1cda95f0c53fbbfd1160cfb Mon Sep 17 00:00:00 2001 From: Felix Faerber Date: Thu, 28 May 2026 11:50:05 +0300 Subject: [PATCH] prod-stack: mount shared pss-key volume on api + worker MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pairs with hosted-gateway commit fcf184b. The api/worker containers now read /data/pss.key on boot — without a shared volume they'd each get their own PSS identity per container, which is what was hanging PSS replies from the provider. Co-Authored-By: Claude Opus 4.7 (1M context) --- hostinger/prod-stack.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/hostinger/prod-stack.yaml b/hostinger/prod-stack.yaml index 7dbceca..6f36fbc 100644 --- a/hostinger/prod-stack.yaml +++ b/hostinger/prod-stack.yaml @@ -14,6 +14,8 @@ volumes: driver: local bee-data: driver: local + pss-key: + driver: local services: @@ -58,6 +60,12 @@ services: REDIS_PORT: 6379 BEE_API_URL: http://bee:1633 HOSTED_GATEWAY_PORT: 8080 + PSS_KEY_PATH: /data/pss.key + volumes: + # Shared PSS key file — all replicas use the same identity so providers' + # PSS replies can be decrypted regardless of which replica handled the + # initial request. + - pss-key:/data networks: - public - internal @@ -96,6 +104,9 @@ services: REDIS_HOST: redis REDIS_PORT: 6379 BEE_API_URL: http://bee:1633 + PSS_KEY_PATH: /data/pss.key + volumes: + - pss-key:/data networks: - internal deploy: