We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🪟 Windows
Any Windows
The startup scripts in the main repo set the NODE_ENV to production. https://github.com/SillyTavern/SillyTavern/blob/5a4e23f62f12d3b91d01d261d52a3e78abff8492/Start.bat#L3
This doesn't happen when using the launcher.
Why is it bad?
How to fix?
Add set NODE_ENV=production at the very start of the launcher.bat or in the server startup string.
set NODE_ENV=production
The text was updated successfully, but these errors were encountered:
this issue has now been fixed at
3c6bca6#diff-a0205db631f5d0cd7cb7ccd40570bf1addb891e7775d7aa8cba136ee3b30834dR21 and a07fa2e
Sorry, something went wrong.
No branches or pull requests
Environment
🪟 Windows
System
Any Windows
Describe the problem
The startup scripts in the main repo set the NODE_ENV to production.
https://github.com/SillyTavern/SillyTavern/blob/5a4e23f62f12d3b91d01d261d52a3e78abff8492/Start.bat#L3
This doesn't happen when using the launcher.
Additional info
Why is it bad?
How to fix?
Add
set NODE_ENV=production
at the very start of the launcher.bat or in the server startup string.Please tick the boxes
The text was updated successfully, but these errors were encountered: