[GH-ISSUE #134] [BUG] XTTS installer fails with Conda error if miniconda_path environment variable not set. #73

New issue

Open

opened 2026-10-15 18:06:45 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-15 18:06:45 +00:00

Owner

Originally created by @Morac2 on GitHub (Jul 25, 2026).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/134

Environment

🍎 Mac

System

26.5.2

Describe the problem

I'm attempting to install XTTS using the install.sh and it gets to the Activating Conda environment: xtts step and fails with a number of errors the first of which is:
./install.sh: line 917: /bin/activate: No such file or directory

The problem is that the script assumes there is a miniconda_path environment variable set to the miniconda 3 path. If it's not set it creates the xtts condo environment, but the rest of the script just fails.

At the very least the install script should abort and inform the user to set the miniconda_path environment variable as once that is properly set to the correct path, the installer works fine.

Additional info

No response

Please tick the boxes

I have explained the issue clearly, and I included all relevant info
I have checked that this issue hasn't already been raised
I have checked the docs

Originally created by @Morac2 on GitHub (Jul 25, 2026). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/134 ### Environment 🍎 Mac ### System 26.5.2 ### Describe the problem I'm attempting to install XTTS using the install.sh and it gets to the Activating Conda environment: xtts step and fails with a number of errors the first of which is: `./install.sh: line 917: /bin/activate: No such file or directory` The problem is that the script assumes there is a miniconda_path environment variable set to the miniconda 3 path. If it's not set it creates the xtts condo environment, but the rest of the script just fails. At the very least the install script should abort and inform the user to set the miniconda_path environment variable as once that is properly set to the correct path, the installer works fine. ### Additional info _No response_ ### Please tick the boxes - [x] I have explained the issue clearly, and I included all relevant info - [x] I have checked that this [issue hasn't already been raised](https://github.com/SillyTavern/SillyTavern/issues?q=is%3Aissue) - [x] I have checked the [docs](https://docs.sillytavern.app/) ![important](https://img.shields.io/badge/Important!-F6094E)

bsakaguchi added the

🐛Bug

🍎 Mac

labels

2026-10-15 18:06:45 +00:00

bsakaguchi commented

2026-10-15 18:06:46 +00:00

Author

Owner

@techdragon commented on GitHub (Aug 8, 2026):

I think relying only on fully initialised and normally installed conda is somewhat of an anti pattern when we could probably make this work, at least on non-windows installs, without conda at all.

@techdragon commented on GitHub (Aug 8, 2026): I think relying only on fully initialised and normally installed conda is somewhat of an anti pattern when we could probably make this work, at least on non-windows installs, without conda at all.

bsakaguchi commented

2026-10-15 18:06:46 +00:00

Author

Owner

@deffcolony commented on GitHub (Aug 8, 2026):

I think relying only on fully initialised and normally installed conda is somewhat of an anti pattern when we could probably make this work, at least on non-windows installs, without conda at all.

@techdragon This repo and its core setup are actually about 3 years old now, and our approach to handling dependencies has definitely evolved over the years. We completely agree that relying on a fully initialized, globally installed Conda has become somewhat of an anti-pattern.

Recently, we've found that the Pixi package manager is way more user-friendly and solves a lot of these exact headaches. We've even started using it for newer modules (like Forge NEO in the launcher).

Pixi keeps the environment directly inside the local project folder. This makes reproduction incredibly easy... you can essentially just share the environment folder without the need to install stuff all over again.

but conda deploys a global folder in C:/Users (on Windows) which most standard users aren't even aware exists. and completely removing a full Conda installation/environment can turn into a bit of a maze. While our launcher's uninstall tool does specifically remove the Conda environment for a targeted app, Pixi's localized approach is just significantly cleaner and better overall.

So yes... we are definitely on the same page about moving away from these global Conda path dependencies. Thanks again for the feedback!

@deffcolony commented on GitHub (Aug 8, 2026): > I think relying only on fully initialised and normally installed conda is somewhat of an anti pattern when we could probably make this work, at least on non-windows installs, without conda at all. @techdragon This repo and its core setup are actually about 3 years old now, and our approach to handling dependencies has definitely evolved over the years. We completely agree that relying on a fully initialized, globally installed Conda has become somewhat of an anti-pattern. Recently, we've found that the Pixi package manager is way more user-friendly and solves a lot of these exact headaches. We've even started using it for newer modules (like Forge NEO in the launcher). Pixi keeps the environment directly inside the local project folder. This makes reproduction incredibly easy... you can essentially just share the environment folder without the need to install stuff all over again. but conda deploys a global folder in C:/Users (on Windows) which most standard users aren't even aware exists. and completely removing a full Conda installation/environment can turn into a bit of a maze. While our launcher's uninstall tool does specifically remove the Conda environment for a targeted app, Pixi's localized approach is just significantly cleaner and better overall. So yes... we are definitely on the same page about moving away from these global Conda path dependencies. Thanks again for the feedback!

bsakaguchi commented

2026-10-15 18:06:46 +00:00

Author

Owner

@techdragon commented on GitHub (Aug 8, 2026):

@deffcolony while I've heard good things about Pixi... I have to point out... this could probably just be "detect available python management tool" -> "use available python management tool"... not "must use conda" or "must use pixi", or "must use pipx", or "must use uvx", etc...

@techdragon commented on GitHub (Aug 8, 2026): @deffcolony while I've heard good things about Pixi... I have to point out... this could probably just be "detect available python management tool" -> "use available python management tool"... not "must use conda" or "must use pixi", or "must use pipx", or "must use uvx", etc...