-
Notifications
You must be signed in to change notification settings - Fork 8
Settings
The jftui settings file is located at ${XDG_CONFIG_HOME}/jftui/settings.
As per freedesktop.org specification, ${HOME}/.config is used as default if ${XDG_CONFIG_HOME} isn't set in the environment.
Each line of the file must be formatted as per the template
key=value
No whitespace is allowed between these three tokens except for the trailing newline character.
(this may change in the future but for now has the advantage of being shell variable assignment syntax, i.e. good for grabbing a valid token in scripts via source... unless value contains whitespace :) )
No comments are allowed.
Keys and values are simply written without being enclosed in quotes, double quotes, back ticks or other delimiters.
The full URL of the Jellyfin server to connect to.
The current session authentication token.
The UserId for the account logged in with the token.
When set to true, libcurl will refuse to connect to your server when its SSL certificate reports a Common Name field or Subject Alternate Name field that doesn't match the URL.
Set to false to disable this check entirely, which can be useful if you're accessing Jellyfin through a reverse proxy but still serving its default, built-in certificate.
Internally, this maps to CURLOPT_SSL_VERIFYHOST.
The above populate the x-emby-authorization header field on login requests, determining how your jftui session will be known to the server and shown in the Devices tab on your dashboard.
Of course, it has no effect to change these until your next login.
This is checked against the compile-time symbol in the binary and remote value on GitHub to give update notifications.
When set to true, jftui fetches the URL https://github.com/Aanok/jftui/releases/latest (reading the Location header field without following the redirect) to check if there is an update available in the repository.
Set to false to disable this for maximum tinfoil hat.
When specified, the mpv core will be instructed to load a corresponding profile listed in mpv.conf.
Being optional, this option needs to be written entirely by hand.
This option instructs jftui whether to try and read the files backing media entries on Jellyfin directly from the local filesystem, when possible.
In case the files result unreachable by the client (e.g. because of permissions), jftui will fall back on requesting media streams from the server over the network.
The option has three possible values:
-
no: always go through network (old behaviour); -
force: always try the local filesystem first; -
yes: try the local filesystem only if the user-provided server address is "localhost", "127.0.0.1" or "[::1]".