Bring the wiki up to date with the server log (#83)
Server Configuration gains a server log step and /logging status in the
checks; Admin Alerts and Moderation say how they relate to the log;
Verification explains the captcha's button without the outdated intent
claim; Host and Container Installation list the message text question and
the intent reminder; Troubleshooting gains 'The server log posts nothing';
Server Log covers setting message text from the setup script; Home,
Configuration and Admin Dashboard mention it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the server log (#81), and the Server Members intent every install now needs
New Server Log page. Bot Setup: switching on Server Members Intent, and the
Required invite now includes View Audit Log (1099797982390). Permissions:
the intents table with the two privileged ones, View Audit Log in the
Required set (14), and the server log in By feature and the admin row.
Commands, Configuration (SERVER_LOG_MESSAGE_CONTENT), Feature Switches, Admin
Dashboard (Logging tab), Home, Troubleshooting (Discord refusing the
connection) and both install pages updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add Container Installation, AWS Hosting and Azure Hosting
Covers the container install (deploy/container-setup.sh) and creating an
EC2 instance or Azure VM for either install, for issue 77. Home, Host
Installation, Configuration, Admin Dashboard and Troubleshooting now cover
both installs, and Troubleshooting explains commands showing up without the
bot (an Install Link with only applications.commands).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document PARIAHBOT_DB_FILE as a development-only override
Bring Host Installation, Configuration and Admin Dashboard up to date (#52)
Host Installation: setup.sh installs only ca-certificates, curl and git
now, and the test server ID is optional (leave it empty in production).
"Data and backups" lists everything the database holds today, and the
backup steps stop the service first, since the WAL-mode database can't
be safely copied while running and the sqlite3 tool isn't installed.
Configuration's sample hom.env leaves GUILD_ID empty.
Admin Dashboard: opening it by name on the local network is a proper
section, now confirmed to work with a plain-http .lan redirect, and it
explains that opening it by IP address is refused (Unknown host).
Permissions page checked (CodeStandards.md § 12): no change needed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the admin dashboard (#13)
New Admin Dashboard page: what it shows and changes per tab, what stays
in Discord, turning it on with setup.sh or by hand, registering the
OAuth2 redirect URL, opening it locally or over an SSH tunnel, who can
sign in, the four settings, its security model, and troubleshooting.
Configuration lists DASHBOARD_PORT, DISCORD_CLIENT_SECRET,
DASHBOARD_HOST and DASHBOARD_PUBLIC_URL; Host Installation describes
setup.sh's new dashboard step; Home and Troubleshooting link it.
Permissions page checked (CodeStandards.md § 12): the dashboard needs
no bot permission of its own and is open only to the bot's owner, noted
alongside who can run each command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document Instagram post alerts (#37)
Add an Instagram Alerts page covering the whole host setup: the
professional account and Page link, the Meta app and its permissions,
the business portfolio and System User, generating a token that never
needs renewing, finding the Instagram account ID, and checking it all
works. It records the steps that failed without them during setup
(linking from the Page side, assigning assets before generating the
token, the PowerShell blank-line trap) and why a System User token is
used instead of a Page token.
Also add /instagram to Commands, Server Configuration, Configuration
and Troubleshooting, link it from Home and Streamer Alerts, and note
that /instagram also uses Mention Everyone for unmentionable roles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document Twitch and YouTube streamer alerts (#17)
New Streamer-Alerts page covering the whole feature from PR #28:
- host credentials: registering a Confidential Twitch app; creating a
YouTube Data API v3 key restricted to that API (console or gcloud)
- hom.env values, and that a restart is needed for them to take effect
- server setup: the alert channel and ping role, self-linking through
the streamer role, and admins adding channels directly
- what gets announced and what doesn't (back catalogue, scheduled
streams, finished-stream recordings, lost streamer role)
- managing the list, and how self-links and admin adds interact
- API limits and cost: Twitch effectively unlimited; the YouTube
10,000-unit daily quota with rough usage by channel count
- known gaps: long-running YouTube streams can be missed, Shorts are
announced, and live and upload alerts share one channel
- testing with high-volume news channels and a public stream on your own
channel
Also:
- Home: description and page table
- Configuration: the three new variables, and the note that hom.env is
only read at startup
- Commands: now 12 commands, the /streamers reference, and
streamer-role's new purpose
- Server-Configuration: a new step 7 for streamer alerts, and
/streamers list in the verification checklist
- Troubleshooting: "Stream or upload alerts don't post", most common
cause first
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add setup wiki: bot setup, host install, configuration, server config, commands, troubleshooting