mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 07:25:52 +03:00
[GH-ISSUE #451] Separate tokens from config #284
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#284
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @peterhoeg on GitHub (Jan 30, 2024).
Original GitHub issue: https://github.com/jpochyla/psst/issues/451
The problem
I would like to standardize my configuration across machines and thus have
$XDG_CONFIG_HOME/Psst/config.jsonread-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.jsonor similar.Alternative solution(s)
I can work around things by using a launcher script that patches
config.jsonbut it's pretty ugly.Additional context
This would also help people who like to keep their config directly in a git (or similar) repository.
@jacksongoode commented on GitHub (Jan 30, 2024):
Is there a standard way of doing this in other applications?
@peterhoeg commented on GitHub (Jan 31, 2024):
The problem isn't unique to psst. As an example,
davmailallows specifying the path to the token file inside the configuration.References:
github.com/mguessan/davmail@2caed4b066/src/etc/davmail.properties (L27-L28)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_HOMEand not$XDG_CONFIG_HOME.