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
* When you first run `stew`, it will look for a `stew.config.json` file. If it cannot find one, then you will be prompted to set the configuration values.
178
+
* After `stew` is installed, you can use the `stew config` command to set the configuration values.
179
+
* At any time, you can manually create or edit the `stew.config.json` file. It should have values for `stewPath` and `stewBinPath`.
180
+
181
+
Make sure that the installation path is in your `PATH` environment variable. Otherwise, you won't be able to use any of the binaries installed by `stew`.
182
+
155
183
# FAQ
156
184
### Why couldn't `stew` automatically find any binaries for X repo?
157
185
The repo probably uses an unconventional naming scheme for their binaries. You can always manually select the release asset.
158
186
159
187
### Will `stew` work with private GitHub repositories?
160
188
Yes, `stew` will automatically detect if you have a `GITHUB_TOKEN` environment variable and allow you to access binaries from your private repositories.
161
-
162
-
### Where does `stew` install binaries?
163
-
The default installation path will depend on your OS:
164
-
| Linux/macOS | Windows |
165
-
| ------------ | ---------- |
166
-
|`~/.local/bin`|`~/AppData/Local/stew/bin`|
167
-
168
-
However, this location can be [configured](https://github.com/marwanhawari/stew/blob/main/config.md).
169
-
170
-
Make sure that the installation path is in your `PATH` environment variable. Otherwise, you won't be able to use any of the binaries installed by `stew`.
0 commit comments