feat: Support raw file paths for certain config values

[JustTemmie]

This would allow config files to be able to link certain values to other text files, like this.

{
  "jellyfin": {
    "url": "http://192.168.1.22:8096",
    "api_key": "/etc/nixos/private/jellyfin-api-key",
    "username": "Temmie"
  },
  "discord": {
    "buttons": [{
        "name": "dynamic",
        "url": "dynamic"
    }]
  },
  "imgur": {
    "client_id": "/etc/nixos/private/imgur-client-id"
  },
  "images": {
    "enable_images": true,
    "imgur_images": true
  }
}

this is extremely useful for NixOS and similar deployments, where i want the config file to be publicly available, but i obviously don't want to share my api keys.

[JustTemmie]

why the fuck does github reference a random ass commit in another repo unrelated to this one wtf

[JustRadical]

I'm not exactly sure what this does

[JustTemmie]

I'm not exactly sure what this does

it tries loading a file from the given value, if it's not a file it just uses the cofig value

[JustRadical]

I dont really see why this would matter for a nix setup, i thought it could generate json files from nix files and if so then you could store the secret in another nix file that doesnt get included or use something like agenix (not sure if this usecase is appropriate)