Skip to content

feat: add docker-compose and deployment guide#11

Open
avlebedinsky wants to merge 4 commits into
nickalie:mainfrom
avlebedinsky:feat/docker-compose-deploy
Open

feat: add docker-compose and deployment guide#11
avlebedinsky wants to merge 4 commits into
nickalie:mainfrom
avlebedinsky:feat/docker-compose-deploy

Conversation

@avlebedinsky

Copy link
Copy Markdown

Summary

  • Add docker-compose.yml for simplified deployment using .env variables
  • Add DEPLOY.md with step-by-step deployment instructions
  • Credentials path is configurable via CLAUDE_CREDENTIALS_PATH env var (cross-platform)
  • Proxy support via HTTP_PROXY / HTTPS_PROXY env vars

Test plan

  • docker compose up -d starts the container successfully
  • Bot responds in Telegram private chat
  • Bot responds in group chat after adding group ID to whitelist

🤖 Generated with Claude Code

Comment thread DEPLOY.md Outdated

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the content here (Telegram bot setup, finding chat IDs, adding groups to whitelist) already exists in README.md. Having it in two places means they'll inevitably drift apart. I'd suggest removing DEPLOY.md and adding a Docker Compose section directly to README.md instead. The compose file and the few compose-specific notes (skills persistence, proxy config) are the only truly new content — everything else is a subset of what the README already covers

Comment thread README.md

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

README.md — The :ro removal from credentials volume mounts is already on main (ef66f97), so those changes can be dropped from this PR

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants