invoke-ai / invoke-ai/InvokeAI

[enhancement]: Stop forcing files onto the C drive.

Open
#8,677 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
28.2k
Forks
3k
Avg merge
6d 5h
Merged PRs (30d)
19

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Contact Details

_No response_

### What should this feature add?

By placing the cache in the Windows user profile by default, you're eating space that the user might not afford. C Drives on modern PCs are often small SSD or M2 drives. Besides that, by forcing the cache to C, you're creating this issue:

Creating virtual environment at: Z:\Invoke\.venv
Activate with: Z:\Invoke\.venv\Scripts\activate
Installing invokeai package...
**> C:\Users\test\AppData\Local\Programs\invoke-community-edition\resources\bin\uv.exe pip install --python 3.12 --python-preference only-managed invokeai==v6.9.0 --force-reinstall --compile-bytecode --index=https://download.pytorch.org/whl/cu128**
Resolved 101 packages in 436ms
Prepared 101 packages in 34ms
░░░░░░░░░░░░░░░░░░░░ [0/101] Installing wheels...
**warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.**

Please allow us choices for file placement. You don't know our space constraints.

**DON'T BE ANOTHER MICROSOFT.**

### Alternatives

There's no workaround. You decided where to put the cache, not me

### Additional Content

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.