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>
Explain setting up the auto-update job that syncs with main Host Installation's auto-update section now covers what the job does and doesn't touch, turning it on (including later, by rerunning setup.sh), what it installs, checking it works and previewing what the next sync brings, changing the schedule, tracking another branch, and turning it off. It also corrects the old claim that the branch is set in the crontab entry too: it's only BRANCH= in the sync script, which Troubleshooting now greps for. Home and the AWS and Azure pages point at it. 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>
Cover the public address prompt, giving admins access and tunnel troubleshooting
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>
Add setup wiki: bot setup, host install, configuration, server config, commands, troubleshooting