[GH-ISSUE #917] Option to store client_id in env var? #1492

New issue

Open

opened 2026-03-14 15:15:02 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 15:15:02 +03:00

Owner

Originally created by @jasonfirkus on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/917

Does this already exist?

**Is your feature already implemented in the latest `master`?** Please go through the [Features README page](https://github.com/aome510/spotify-player?tab=readme-ov-file#features) to make sure your request feature hasn't been implemented. - No

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Yes, I do not want to commit "client_id" to my public dotfiles repo

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add support for a SPOTIFY_PLAYER_CLIENT_ID env var or similar.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @jasonfirkus on GitHub (Feb 5, 2026). Original GitHub issue: https://github.com/aome510/spotify-player/issues/917 **Does this already exist?** <br> **Is your feature already implemented in the latest `master`?** Please go through the [Features README page](https://github.com/aome510/spotify-player?tab=readme-ov-file#features) to make sure your request feature hasn't been implemented. - No **Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] - Yes, I do not want to commit "client_id" to my public dotfiles repo **Describe the solution you'd like** A clear and concise description of what you want to happen. - Add support for a SPOTIFY_PLAYER_CLIENT_ID env var or similar. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.