You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modern *nix-based applications use the XDG path standard for configuration and data. It used to be that everyone stored things under a dot-dir in the home directory, but this clutters the home directory and doesn't give the user much say in where things are stored. Most *nix systems now have XDG_* environment variables set that specify where apps should store their configuration and data files.
Right now, tabby-agent hard-codes configs AND data under the same folder in the user's home dir.
Instead, tabby should use XDG_* dirs for any paths that write to filesystem to give users the control they expect when using a *nix system.
In my case this is convenient because now I can make my all configurations portable, trusting they will all be in the same place while keeping non-config data such as logs or databases separate.
It's not such a big deal with the server as I can specify the volume mount for the docker server (eg, $XDG_DATA_DIR/tabby or /.local/share/tabby.
The text was updated successfully, but these errors were encountered:
Modern *nix-based applications use the XDG path standard for configuration and data. It used to be that everyone stored things under a dot-dir in the home directory, but this clutters the home directory and doesn't give the user much say in where things are stored. Most *nix systems now have
XDG_*
environment variables set that specify where apps should store their configuration and data files.Right now, tabby-agent hard-codes configs AND data under the same folder in the user's home dir.
Instead, tabby should use
XDG_*
dirs for any paths that write to filesystem to give users the control they expect when using a *nix system.In my case this is convenient because now I can make my all configurations portable, trusting they will all be in the same place while keeping non-config data such as logs or databases separate.
It's not such a big deal with the server as I can specify the volume mount for the docker server (eg,
$XDG_DATA_DIR/tabby
or/.local/share/tabby
.The text was updated successfully, but these errors were encountered: