[GH-ISSUE #1092] Does spotify-tui support env variables in its client.yml? #504

New issue

Closed

opened 2026-02-28 14:49:33 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:49:33 +03:00

Owner

Originally created by @JohnCarterGonzalez on GitHub (Jul 6, 2023).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1092

I have my .config/spotify-tui/client.yml file like:

   client_id: ${SPT_CLIENT_ID}
   client_secret: ${SPT_CLIENT_SECRET}
   device_id: ${SPT_DEVICE_ID}
   port: 8888

which references the env variables of spotify api. The main reason I am using env variables, is for commiting my config files. Is there a step I am missing? When I run: echo $SPT_CLIENT_ID in the shell, the output is as expected. Yet when I run spt, it returns "INVALID CLIENT". Any help would be appreciated, thanks!

Originally created by @JohnCarterGonzalez on GitHub (Jul 6, 2023). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1092 I have my .config/spotify-tui/client.yml file like: ```yaml client_id: ${SPT_CLIENT_ID} client_secret: ${SPT_CLIENT_SECRET} device_id: ${SPT_DEVICE_ID} port: 8888 ``` which references the env variables of spotify api. The main reason I am using env variables, is for commiting my config files. Is there a step I am missing? When I run: `echo $SPT_CLIENT_ID` in the shell, the output is as expected. Yet when I run `spt`, it returns "INVALID CLIENT". Any help would be appreciated, thanks!