mirror of
https://github.com/SillyTavern/SillyTavern-Launcher.git
synced 2026-11-05 00:27:39 +00:00
[GH-ISSUE #31] start_command error when launching SillyTavern + Extra on Windows #9
Labels
No labels
🚏 Awaiting User Response
🐛Bug
🐛Bug
🐛Bug
🦄 Feature Request
✅ Fixed
✅ Fixed
👩💻 Good First Issue
‼️ High Priority
🧑💻 In Progress
🐧 Linux
🐧 Linux
💤 Low Priority
🍎 Mac
❕ Medium Priority
pull-request
🪟 Windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Launcher#9
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?
Originally created by @Greanibak on GitHub (Dec 29, 2023).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/31
Originally assigned to: @deffcolony on GitHub.
Hello guys,
With SillyTavern 1.11.1 'release' (736223a8), I encountered a bug when launching SillyTavern Extras using launcher.bat, specifically with command 3. The CMD window would open but then end with an error related to the start_command not being defined. I noticed that the SillyTavern launcher.bat was sourcing the modules.txt not from the "SillyTavern-extras" folder but from the SillyTavern root folder. Moreover, even the modules.txt in the SillyTavern folder doesn't seem to work on Windows, as it lacks the "start_command" at the beginning, as well as the server.py. The parsing intended by the code doesn't seem to function.
I resolved this on my end by editing the modules.txt file in the root folder and adding the complete API server launch command with the start_command:
start_command=python server.py --enable-modules=chromadb --listen (in my case, I only want listen and chromadb).
Did I miss something on my end, or is this a problem encountered by others as well? Thank you.
@deffcolony commented on GitHub (Dec 31, 2023):
@Greanibak Yes, I now notice the issue. It occurs right now when you open the launcher.bat for the first time. The script generates a file called
modules.txtin the current directory where it is being run. You need to modify the modules you wish to enable using the Edit Extras Modules option. that is located at:/ Home / Toolbox / Edit Extras Modulesthe start command will work when you activate the modules you wantUPDATE: I updated the launcher.bat so it will let you know if you need to enable atleast 1 module for extras
@deffcolony commented on GitHub (Mar 28, 2024):
@Greanibak
I've implemented some changes to the launcher.bat script to address the issue you reported. Before closing the issue, could you please let me know if you're still encountering any issues with the modules? otherwise i will close this issue
@Greanibak commented on GitHub (Mar 29, 2024):
Thanks you very much,
you can close this issue.