You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of my config files are publicly visible and are deployed in a read-only state with GNU Guix. As such, I don't have an easy way to store an Acoustid API key in the Beets config file without going through a whole song and dance. (Rename the symlink, copy the file contents, paste into a new config.yml, add the API key, submit fingerprints, delete the new config.yml, restore the symlink.)
I (and hopefully others) would find it grand if beet submit could accept an API key from the command line when it was invoked.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
Most of my config files are publicly visible and are deployed in a read-only state with GNU Guix. As such, I don't have an easy way to store an Acoustid API key in the Beets config file without going through a whole song and dance. (Rename the symlink, copy the file contents, paste into a new
config.yml
, add the API key, submit fingerprints, delete the newconfig.yml
, restore the symlink.)I (and hopefully others) would find it grand if beet submit could accept an API key from the command line when it was invoked.
Beta Was this translation helpful? Give feedback.
All reactions