mirror of
https://github.com/SillyTavern/SillyTavern-Docs.git
synced 2026-10-16 02:11:54 +00:00
[PR #127] [MERGED] Update remote-connections.md: Use config.yaml Instead of whitelist.txt for Remote Connection Setup #133
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Docs#133
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/SillyTavern/SillyTavern-Docs/pull/127
Author: @RivelleDays
Created: 2/1/2025
Status: ✅ Merged
Merged: 2/2/2025
Merged by: @Cohee1207
Base:
main← Head:main📝 Commits (4)
f2e236cUpdate remote-connections.md93fb7d2Update remote-connections.md1a58b98Update remote-connections.md9f49d8dUpdate remote-connections.md📊 Changes
1 file changed (+71 additions, -32 deletions)
View changed files
📝
Administration/remote-connections.md(+71 -32)📄 Description
While helping some friends set up remote connections, I noticed that many had trouble using
whitelist.txt. Editingconfig.yamldirectly seemed to be a more convenient and reliable approach. After discussing this with Wolfsblvt in sillytavern-help, I decided to update the documentation to reflect this method.Changes
config.yamlas the primary approach and adjust the documentation accordinglywhitelist.txtmethod (but mark it as not recommended)Personal Note:
I noticed this document was originally written by ceruleandeep. They’ve been incredibly kind and have helped me a lot with Traditional Chinese i18n. Honestly, they’re a big reason I fell in love with SillyTavern in the first place. I really appreciate them—and, well, I just think they’re amazing ; v ;
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.