kitestacks-homelab/projects/Discord Integration/RUNBOOK.md
KiteStacks AutoSync e409b461d8 security: redact all IPs, ports, and passwords from docs
Replace all production IPs (public, LAN, Tailscale), host port bindings,
and hardcoded passwords/secrets across RUNBOOK.md, docs/, and projects/
with descriptive placeholders (<KSCLOUD1_PUBLIC_IP>, <port>,
<KSCLOUD1_SUDO_PASSWORD>, etc.) so no sensitive infrastructure details
are committed to the repository.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-11 16:05:53 -05:00

75 lines
1.3 KiB
Markdown

# Discord Integration Runbook
## Test Portal
Directory:
/home/kenpat/docker/kitestacks-portal-test
URL:
http://<MONK_LAN_IP>:<port>
## Website Files Modified
public/index.html
public/style.css
public/images/icons/discord.png
## Discord Card
The Discord card is located in the Community panel.
Current invite:
https://discord.gg/QbdveTb6Kw
## Access Workflow
Visitor opens KiteStacks website.
Visitor clicks Discord.
Visitor joins Discord server.
Visitor reads welcome and rules.
Visitor requests access.
Admin approves user.
Approved user receives member access.
## Planned Channels
Public:
#welcome
#rules
#request-access
Member:
#general
#recent-activity
#announcements
#homelab-showcase
Admin:
#staff
#applications
#moderation
## Recent Activity Channel
Discord Channel:
#recent-activity
Purpose:
This channel acts as the live activity feed for KiteStacks.
It should show:
- Website updates
- Homelab service changes
- Documentation updates
- Forgejo repository commits
- Infrastructure changes
- Future deployment notices
Documentation Access:
If a user wants details about a change, they should be directed to the related documentation inside the Forgejo repository.
Main documentation path:
projects/Discord Integration/
Changelog file:
projects/Discord Integration/CHANGELOG.md