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
Currently, scoop looks for the config file at ~/.config/scoop/config.json. While this works well for most use cases, it would be great to have more flexibility in terms of the location of the config file.
One use case for this is portability. I like to be able to carry scoop and apps in my portable SSD, while with the current implementation, the config file is always looked for in the user directory - which doesn't makes it truely portable.
To address this, I propose the addition of an environment variable $SCOOP_CONFIG. If this variable is set, scoop would scan for the config file at the specified location. If the variable is not set, the default behavior of looking for the config file in the user directory would be taken place.
The text was updated successfully, but these errors were encountered:
Hey there,
Currently, scoop looks for the config file at
~/.config/scoop/config.json
. While this works well for most use cases, it would be great to have more flexibility in terms of the location of the config file.One use case for this is portability. I like to be able to carry scoop and apps in my portable SSD, while with the current implementation, the config file is always looked for in the user directory - which doesn't makes it truely portable.
To address this, I propose the addition of an environment variable
$SCOOP_CONFIG
. If this variable is set, scoop would scan for the config file at the specified location. If the variable is not set, the default behavior of looking for the config file in the user directory would be taken place.The text was updated successfully, but these errors were encountered: