Put config files in $XDG_CONFIG_HOME/dbeaver instead of ~/.dbeaver as per basedir-spec
See original GitHub issuedbeaver shouldn’t use user’s root directory to store configuration files, as per freedesktop spec and basedir-spec
Here’s a preview :
$XDG_CONFIG_HOME defines the base directory relative to which user specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.
On Windows, if $XDG_CONFIG_HOME
is not set, %appdata%\dbeaver
, %localappdata%\dbeaver
or %userprofile%\.config\dbeaver
should be used.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:10 (6 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Version 6.1.3 will use new workspace format and new location workspace location.
${XDG_DATA_HOME}/DBeaverData
~/Library/DBeaverData
%AppData%/DBeaverData
If XDG_DATA_HOME is not set then
~/.local/share
folder will be used on Linux.On first start DBeaver 6.1.3+ will ask about workspace migration and will automatically copy/convert all configurations.
Not really.
$XDG_CONFIG_HOME
is not a place for binaries (like drivers) or logs. This directory is supposed to be user-level/etc
directory, so in ideal world only configuration files should be stored here.Drivers downloaded by DBeaver should go to
$XDG_DATA_DIR
- user-level/usr/share
.Logs, temporary files etc. should go to
$XDG_CACHE_DIR
- user-level/var
.There is also
$XDG_RUNTIME_DIR
, as name suggests, used only during runtime - user-level/run
,/var/run
,/var/lock
etc. - good place for.lock
file (or other kinds of data that could be shared between running instances of an application).