docs(docker): clarify userbot mode in compose/run-bot, bot token optional

This commit is contained in:
javis-bot
2026-06-12 21:26:00 +09:00
parent 8a2a109d5e
commit f89246a14d
2 changed files with 9 additions and 5 deletions

View File

@@ -7,9 +7,11 @@
# Just bring it up — everything (incl. Ollama models) comes up automatically:
# docker compose up -d --build
#
# The Discord token can be added LAST: without it the desktop, brain bridge,
# Ollama and models all run; only the bot waits. Then put DISCORD_BOT_TOKEN in
# .env and re-run `docker compose up -d`.
# The Discord credential can be added LAST: without it the desktop, brain
# bridge, Ollama and models all run; only the bot waits. This deployment runs
# in userbot mode, so put DISCORD_SELFBOT_TOKEN in .env and re-run
# `docker compose up -d`. (A normal-bot DISCORD_BOT_TOKEN is optional and only
# needed for the legacy slash-command bot; leave it blank for userbot mode.)
#
# Watch the desktop: VNC viewer -> localhost:5901 (or browser -> localhost:6080)
# ============================================================================

View File

@@ -1,9 +1,11 @@
#!/usr/bin/env bash
# Wait for the brain bridge, then run the Discord bot.
#
# The Discord token is intentionally deferred: if DISCORD_BOT_TOKEN is not set
# The Discord credential is intentionally deferred: if no usable token is set
# yet, the rest of the stack (desktop, bridge, ollama) still runs fully. The bot
# just waits. Add the token to .env and `docker compose up -d` to start it.
# just waits. Add a token to .env (DISCORD_SELFBOT_TOKEN for userbot mode, or
# DISCORD_BOT_TOKEN + DISCORD_APP_ID for the legacy normal bot) and
# `docker compose up -d` to start it.
set -e
cd /app/bot