Xentara v2.0.4
User Manual
Location of the OAuth 2.0 Configuration File

Default Location

Linux

Under Linux, Xentara looks for the OAuth 2.0 configuration file in a number of default directories, until it finds a file named oauth2.json. The following locations are tried, in order:

  • ${HOME}/.config/xentara/oauth2.json
  • /etc/xdg/xentara/oauth2.json

You can specify additional search directories on the command line using the option --config-dir=<path>, where <path> is be the path to a directory to search. You can specify this option more than once to add multiple directories to the search path. The additional directories are searched in the order they appear on the command line, before the default directories listed above.

Note
The equal signs can be omitted from options to facilitate file name completion when using the bash shell. This means that you can write --config-dir <path> instead of --config-dir=<path>.

You can override the searched directories as described in the XDG Base Directory Specification.

Windows

Under Windows, Xentara looks for the OAuth 2.0 configuration file in a number of default directories, until it finds a file named oauth2.json. The following locations are tried, in order:

  • %LOCALAPPDATA%\Xentara\Config\oauth2.json
  • %ProgramData%\Xentara\Config\oauth2.json

You can specify additional search directories on the command line using the option -ConfigDir <path>, where <path> is be the path to a directory to search. You can specify this option more than once to add multiple directories to the search path. The additional directories are searched in the order they appear on the command line, before the default directories listed above.

Custom Location

You can specify a different OAuth 2.0 configuration file on the command line using the option --oauth2=<path> under Linux, or -OAuth2 <path> under Windows. <path> must be the path to the OAuth 2.0 configuration file.

Note
Under Linux, the equal signs can be omitted from options to facilitate file name completion when using the bash shell. This means that you can write --oauth2 <path> instead of --oauth2=<path>.