github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-07-16 13:21:57 -05:00
Code Issues 9.3k Packages Projects Releases Wiki Activity

[PR #781] Add NapCat and qq-ai-bot compose sample #16682

New Issue
Open
opened 2026-07-10 18:49:34 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-10 18:49:34 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/781
Author: @happysnaker
Created: 7/3/2026
Status: 🔄 Open

Base: master ← Head: feat/napcat-qq-ai-bot-sample

📝 Commits (1)

  • 65dd32a Add NapCat and qq-ai-bot compose sample

📊 Changes

4 files changed (+215 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)
➕ napcat-qq-ai-bot/README.md (+120 -0)
➕ napcat-qq-ai-bot/compose.yaml (+69 -0)
➕ napcat-qq-ai-bot/napcat.onebot11.reverse-ws.json (+25 -0)

📄 Description

Summary

  • add a new napcat-qq-ai-bot Docker Compose sample under the "basic setups" section
  • show a messaging-native local stack using NapCat for QQ / OneBot transport and qq-ai-bot as the ACP bridge
  • keep the sample intentionally local-development oriented with the built-in mock ACP agent for deterministic first-run validation

Why this sample is useful

Most Compose examples around AI focus on web UIs, model serving, or generic chat apps. This sample demonstrates a different but real integration shape:

QQ -> NapCat / OneBot 11 -> qq-ai-bot -> ACP-compatible agent

That gives Compose users one concrete reference for a message-channel deployment path, not only browser-facing apps.

What is included

  • compose.yaml for napcat + qq-ai-bot
  • a matching NapCat OneBot reverse-WS config file
  • a README that documents the local-validation flow, ports, login path, token note, health endpoints, and how to replace the mock ACP agent with a real one

Project page: https://happysnaker.github.io/qq-ai-bot/

Notes

  • this stays aligned with the repository's local / tinkering scope and is explicitly not framed as production-ready
  • the sample uses the published ghcr.io/happysnaker/qq-ai-bot:latest image
  • I validated the Compose file shape with docker compose config

Closes #780

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/781 **Author:** [@happysnaker](https://github.com/happysnaker) **Created:** 7/3/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feat/napcat-qq-ai-bot-sample` --- ### 📝 Commits (1) - [`65dd32a`](https://github.com/docker/awesome-compose/commit/65dd32aba701db0fa69c5330bbc06368f529f325) Add NapCat and qq-ai-bot compose sample ### 📊 Changes **4 files changed** (+215 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) ➕ `napcat-qq-ai-bot/README.md` (+120 -0) ➕ `napcat-qq-ai-bot/compose.yaml` (+69 -0) ➕ `napcat-qq-ai-bot/napcat.onebot11.reverse-ws.json` (+25 -0) </details> ### 📄 Description ## Summary - add a new `napcat-qq-ai-bot` Docker Compose sample under the "basic setups" section - show a messaging-native local stack using NapCat for QQ / OneBot transport and qq-ai-bot as the ACP bridge - keep the sample intentionally local-development oriented with the built-in mock ACP agent for deterministic first-run validation ## Why this sample is useful Most Compose examples around AI focus on web UIs, model serving, or generic chat apps. This sample demonstrates a different but real integration shape: ```text QQ -> NapCat / OneBot 11 -> qq-ai-bot -> ACP-compatible agent ``` That gives Compose users one concrete reference for a message-channel deployment path, not only browser-facing apps. ## What is included - `compose.yaml` for `napcat` + `qq-ai-bot` - a matching NapCat OneBot reverse-WS config file - a README that documents the local-validation flow, ports, login path, token note, health endpoints, and how to replace the mock ACP agent with a real one Project page: https://happysnaker.github.io/qq-ai-bot/ ## Notes - this stays aligned with the repository's local / tinkering scope and is explicitly not framed as production-ready - the sample uses the published `ghcr.io/happysnaker/qq-ai-bot:latest` image - I validated the Compose file shape with `docker compose config` Closes #780 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-07-10 18:49:34 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#16682
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?