prod-stack: mount shared pss-key volume on api + worker
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) <noreply@anthropic.com>
This commit is contained in:
1 parent
c6879f1a79
commit
050e10e284
1 file changed
+11
@@ -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:
|
||||
|
||||
Reference in new issue
Block a user