Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEAT: consider changing the dbgate-data directory that is created in HOME #248

Closed
devtrends opened this issue Mar 22, 2022 · 4 comments
Closed
Labels
accepted+planned Accepted and planned to be released in near future Released in BETA

Comments

@devtrends
Copy link

Is your feature request related to a problem? Please describe.
Under linux, dbgate creates a visible, dbgate-data folder directly in the user's home directory. This is not typical Linux behaviour and it clutters the home directory.

Describe the solution you'd like
Store this data in a .config sub-directory e.g. ~/.config/dbgate-data/

Alternatively, change the current directory to ~/.dbgate-data/

@janproch
Copy link
Member

Good point! I will do this, it will require moving data into new location, but this should be definitely done

janproch added a commit that referenced this issue May 17, 2022
@janproch janproch added accepted+planned Accepted and planned to be released in near future Released in BETA labels May 19, 2022
@janproch
Copy link
Member

janproch commented May 23, 2022

Changed in 5.0.0

dbgate-data directory was renamed to .dbgate, for all platforms (mac, linux, windows)

Under Windows, this is probably not most used behaviour, but many programs (eg. VSCode) use the same convention

@ethanmlee
Copy link

ethanmlee commented Jun 1, 2022

You may want to change this in the docker-compose example on docker hub. I ran into some problems until I saw this change. So change the following from the docker hub page:

    volumes:
      - dbgate-data:/root/dbgate-data

to this:

    volumes:
      - dbgate-data:/root/.dbgate

You could also symlink /root/.dbgate/ to /root/dbgate-data in the dockerfile do ensure compatibility with older docker-compose files

Thanks!

@janproch
Copy link
Member

janproch commented Jun 2, 2022

@ethanmlee Thanks, updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted+planned Accepted and planned to be released in near future Released in BETA
Projects
None yet
Development

No branches or pull requests

3 participants