c_webui.sh conda installation installs almost entirely outside ./env

[sdrakulich]

regarding c_webui.sh

doesn't properly activate the ./env environment, and hence, installs packages in base, in the user's site packages, etc

even with the properly activated ....lollms-webui/env environment, launching the webui and attempting to install bindings results in them installing to the global environment (to ~/.local/lib/python3.10/site-packages, not even in conda base env). Even if I activate the base env, then activate the ./env, and then run python app.py, it still behaves this way.

I use mamba, but it should be besides the point. Was using the UI nicely beforehand, but in nested conda env (made my own lollms env located in ~/mambaforge/envs/lollms, and then ran c_webui.sh). This led to a ~10 gig ~/mambaforge/envs/lollms dir, and ~400mb ./env dir in the actual lollms-webui cloned repo dir.

If I understand correctly, the script should be installing everything within ./env. The environment fails to activate for whatever reason, even though I can manually conda activate ./env after the fact.

Expected: Everything installed to ./env, except gcc and maybe cudatoolkit-dev, but hopefully even that is sequestered to ./env

Hopefully this gets resolved, I know you're working on many levels simultaneously. Thank you for your work!

[ParisNeo]

Hi there. The thing is I only made and tested the windows version of the conda installation scipt. It does install in the right env folder. In linux, I basically wrote the script without testing as I had no linux machines these days.

I'll try to test next week and I'll see where is the problem.

Thanks for notifying me.