Use Scout on Windows Server (2008) with multiple developers.

[Ap4ch32013]

Hi,

We are trying to use Scout on a windows 2008 server.

We want to run it similarly to how it runs on *nix using a scheduler (cron).

We have tried setting it up as a task scheduler job, and the executable runs.

However it will not update files or see changes.

Is there a way to run Scout from the windows task scheduler?

The reason we want to do this is that we have multiple developers and they cannot all log into the server and start up scout every time they make a change.

Kind Regards

Adrian Ramos

[TheJaredWilcurt]

I've added this to the Project Road Map for future versions of Scout-App.

I know how to implement this, however I'm not sure how best to document this feature so those in the future won't need to create an issue requesting an already implemented feature.

1. Basically you would open your scout-settings.json file located here:

   • Windows: %LOCALAPPDATA%/scout-app/scout-settings.json
   • Linux: ~/.config/scout-app/scout-settings.json
   • OSX: ~/Library/Application Support/scout-app/scout-settings.json

2. Copy the project ID you would want to run on startup.

3. Run Scout-App and pass in the ID's separated by commas, like so:

   Scout-App.exe sa1470398543266,sa1470402556882
   

So obviously, I'd need to give people an easier means of accessing the Project ID. That can be added to a right-click or something. But I'm not sure how to communicate the CLI functionality other than in the README on GitHub.

Anyways, we still have some time to figure that out before this feature is implemented.

Also, note that the scout-settings.json file is User account specific. So if you have multiple people logging in, each would have their own separate projects. I guess a global install could be done as an option if requested. But a different issue would need to be created for that.

[TheJaredWilcurt]

In #69 there is a suggestion to allow for projects to start running on app launch. This could be a simple checkbox in the project's settings panel, by the environment settings or something. Although I don't think it negates all use cases for a CLI argument of project ID's, I do think it makes the process a lot more intuitive and functional for most use cases that would want to use the CLI method.