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

File structure of client configuration directories #26

Closed
ErikBjare opened this issue Jan 4, 2017 · 2 comments
Closed

File structure of client configuration directories #26

ErikBjare opened this issue Jan 4, 2017 · 2 comments
Milestone

Comments

@ErikBjare
Copy link
Member

On Linux, all user-level config files should be stored in a subdirectory of $XDG_USER_CONFIG (defaults to $HOME/.config) according to XDG spec.

Currently we have an issue where we don't place the configuration files of different modules in a consistent manner. We currently use appdirs for this in a lot of places, we should consider putting a function get_global_config_dir() and get_config_dir(module_name) in the aw-core package which is used everywhere. We might also want a get_log_dir(), even though it might end up only being used in aw_core.log.

We might also want to consider $XDG_DATA_HOME (defaults to $HOME/.local/share) for data such as databases (sqlite etc.) managed by aw-server. We might even want to consider $XDG_CACHE_HOME in case we ever want to cache some dataviews presented by aw-server for instance (which is likely).

@ErikBjare
Copy link
Member Author

Fixed for logs in: ActivityWatch/aw-core#13

@ErikBjare ErikBjare changed the title File structure of configuration directory File structure of client configuration directories Jan 5, 2017
@ErikBjare
Copy link
Member Author

Done with the barrage of unified-dirs PRs.

@ErikBjare ErikBjare modified the milestones: v0.7, v0.8 May 29, 2017
vasuemme111 pushed a commit to vasuemme111/activitywatch that referenced this issue Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant