Skip to content

Config file not being read on Windows / invidious instance cannot be changed #110

@ayrtonoropeza

Description

@ayrtonoropeza

Platform: Windows 11
ytui version: 1.0.1
Installation method: ytui_v1.0.1_Windows_x86_64.zip binary, extracted and placed in C:\Users\USERNAME\AppData\Local\Microsoft\WindowsApps\ (already on PATH, so no admin required).

Description

On Windows, ytui does not read the config file regardless of where it is placed, making it impossible to change settings — including the invidious instance, which is hardcoded by default to invidious.jing.rocks. This instance, always returns this error on my machine:

Error: Get "https://invidious.jing.rocks/api/v1/search?page=1&q=asfddasf&region=US&type=video": dial tcp: lookup invidious.jing.rocks: no such host

Steps to reproduce

  1. Install ytui on Windows 11
  2. Run it once
  3. Check %USERPROFILE%\.config\ytui\config.yaml. If it doesn't exist, create it and set a custom invidious.instance value. (I did the same in %APPDATA%\ytui\config.yaml just in case, since I'm not sure where the user config dir is actually located on Windows)
  4. Run ytui and search for a video.

Expected behavior

ytui reads the config file and uses the specified invidious instance, showing you a list of videos for your query.

Actual behavior

ytui ignores the config file entirely regardless of location. The default invidious instance (invidious.jing.rocks) is always used, and it doesn't work. No config file is auto-generated on first run in any of the locations tried, making it hard to even discover the correct path.


The README states the config path is $HOME/.config/ytui/config.yaml, but this is documented from a Linux/macOS perspective. On Windows, $HOME and $XDG_CONFIG_HOME are not natively set, so the resolved path is ambiguous.

Would it be possible to either document the correct Windows config path explicitly, auto-generate the config on first run, or print the resolved config path on startup?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions