Minecraft-Server

Go to file

Paul Kloppers b99c36c13c fix(bot): scope /up to server+tunnel — bare compose up -d killed the bot

actUpAll was running `docker compose up -d` with no service filter, so it
re-evaluated every service in the project (including the bot). docker
compose then recreated the bot container, SIGTERM'd the running process
mid-RPC, and left a renamed replacement (`<oldhash>_minecraft-bot`) stuck
in "Created" state because the original container hadn't yet released
the name. End result: /up silently took the bot offline and required
manual `docker rm + docker compose up -d bot` to recover.

Scope to SERVER_SVC + PF_SVC (matching actDownAll which already does the
same thing). The bot can't sensibly restart itself anyway.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-13 23:13:42 +02:00

bot

fix(bot): scope /up to server+tunnel — bare compose up -d killed the bot

2026-05-13 23:13:42 +02:00

data

add telegram bot and autossh tunnel

2026-05-11 21:51:59 +02:00

mcp

stream Redstone replies via sendMessageDraft + fix self-killing server_down

2026-05-12 08:47:35 +02:00

.gitignore

feat(redstone): add OpenRouter primary AI with Gemini fallback