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

Separate tokens from config #451

Open
peterhoeg opened this issue Jan 30, 2024 · 2 comments
Open

Separate tokens from config #451

peterhoeg opened this issue Jan 30, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@peterhoeg
Copy link

peterhoeg commented Jan 30, 2024

The problem
I would like to standardize my configuration across machines and thus have $XDG_CONFIG_HOME/Psst/config.json read-only. That is however not possible with the tokens being written there.

Possible solution
If the tokens could be stored in a separate file such as $XDG_CONFIG_HOME/Psst/creds.json or similar.

Alternative solution(s)
I can work around things by using a launcher script that patches config.json but it's pretty ugly.

Additional context
This would also help people who like to keep their config directly in a git (or similar) repository.

@Insprill Insprill added the enhancement New feature or request label Jan 30, 2024
@jacksongoode
Copy link
Collaborator

Is there a standard way of doing this in other applications?

@peterhoeg
Copy link
Author

The problem isn't unique to psst. As an example, davmail allows specifying the path to the token file inside the configuration.

References:

Come to think of it - since many people store a lot of their dotfiles in a repository, if the path isn't configurable, it should probably be under $XDG_STATE_HOME and not $XDG_CONFIG_HOME.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants