Sync the self-hosting stack (8342e2e)
This commit is contained in:
+11
-2
@@ -51,7 +51,7 @@ services:
|
||||
retries: 10
|
||||
|
||||
api:
|
||||
image: ${JARVIS_IMAGE_API:-git.luxit.be/luxit/jarvis-api:latest}
|
||||
image: ${JARVIS_IMAGE_API:-git.luxit.be/luxit/jarvis-api:stable}
|
||||
restart: unless-stopped
|
||||
# The assistant runs long operations, and a deploy is the most common thing that interrupts one.
|
||||
# Given room to stop, the API aborts each loop, writes the partial answer with a note saying why
|
||||
@@ -103,6 +103,15 @@ services:
|
||||
# Required to create new organizations, users or agents. Without it an instance keeps running
|
||||
# everything it already has, creates nothing new, and contacts nobody. See the README.
|
||||
JARVIS_LICENSE_KEY: ${JARVIS_LICENSE_KEY:-}
|
||||
# Which distribution channel this instance follows, shown to signed-in operators beside the
|
||||
# version numbers. Set `JARVIS_CHANNEL=stable` (or `dev`) in .env if you track a channel;
|
||||
# LEAVE IT EMPTY IF YOU PIN EXACT VERSIONS, because then you follow no channel — you follow a
|
||||
# decision — and the footer shows nothing rather than a label that stopped being true.
|
||||
#
|
||||
# It is not baked into the image, and cannot be: a channel is decided after a build and moves
|
||||
# afterwards, so the same image is `dev` one week and `stable` the next. Only you know which
|
||||
# one you are on.
|
||||
APP_CHANNEL: ${JARVIS_CHANNEL:-}
|
||||
|
||||
AGENT_HEARTBEAT_INTERVAL_SEC: ${AGENT_HEARTBEAT_INTERVAL_SEC:-30}
|
||||
RUN_SHUTDOWN_GRACE_SEC: ${RUN_SHUTDOWN_GRACE_SEC:-25}
|
||||
@@ -124,7 +133,7 @@ services:
|
||||
start_period: 40s
|
||||
|
||||
web:
|
||||
image: ${JARVIS_IMAGE_WEB:-git.luxit.be/luxit/jarvis-web:latest}
|
||||
image: ${JARVIS_IMAGE_WEB:-git.luxit.be/luxit/jarvis-web:stable}
|
||||
restart: unless-stopped
|
||||
depends_on:
|
||||
- api
|
||||
|
||||
Reference in New Issue
Block a user