Replies: 2 comments
-
|
Well, maybe put the files in C:\Stash and copy the config yaml files to that folder. This way you should be able to get the same result for all the users. |
Beta Was this translation helpful? Give feedback.
-
|
It's documented in the setup page, but I'm not sure it is elsewhere: when you start stash, it first looks for The solution to your issue is likely to move the contents to a folder that is accessible to all users, and copy the stash exe file to that same directory. When you run stash from that directory, it should pick up the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Scope
I installed Stash while I was logged in remotely via RDP (say, user-remote); When I logged in locally, under another user (say, user-local), I end up on the http://localhost:9999/setup page again, where I have to reconfigure again, scan again, etc.
Long Form
Naturally, this is to be expected, as the default user config yaml files are in the C:\Users<specific-user>;
So I copied the C:\Users\user-remote\.stash folder onto C:\Users\user-local\.stash, and made some edits to the config.yml file, but I am still being asked to reconfig, scan again.
Wiki Topic
What would be good is a Wiki topic covering this issue, or a
How Toinstructions on what to do exactly, such that the use-case I described is catered for, i.e. install is for the machine, not a specific user.Beta Was this translation helpful? Give feedback.
All reactions