@tinvm I just saw the issue you logged on Github. I think you're asking how to specify a specific username for the sudo command? If that's the case, the unfortunate answer is you cannot specify a user. The sudo command is used primarily to elevate a user's permissions without prompting them, but this does not work on all versions of Windows (it is particularly problematic on Windows 7). If that's not what you're asking, please clarify.
@JimmyHodgson - node-windows supports a "flag" attribute (an array, I believe), which was added in PR #76 (https://github.com/coreybutler/node-windows/pull/76/files)
I don't think it's documented in the README and should be
(I didn't write that code, so I'm not really that familiar with it)
hi I am trying to use node-windows to run my react node js project. To start the application I run the below script,
cross-env VIRTUAL_HOST=127.0.0.1 BABEL_ENV=development babel-node ./webpack/dev-server.js
What do I run it using node-windows? what will be the entry for script: 'app.js', in install.js
@AmiteswarRoy - take a look at https://github.com/coreybutler/node-windows#environment-variables
@rodolfoviolac - have you seen https://github.com/coreybutler/node-windows/wiki?
my svc.exists() is reporting TRUE but I'm not finding my service in the Windows Services manager and no app listening on my port...
Anyone tried to get node-windows working with pkg? I just followed the pkg instructions and im getting a weird error like this:
Error: File 'C:\**\uploader-service\node_modules\node-windows\bin\winsw\winsw.exe' was not included into executable at compilation stage. Please recompile adding it as asset or script.
I just want my service installer to be a exectuable, so perhaps there is a different way than using pkg. Any ideas?
@alexlpze_twitter - not directly. It depends on your use case though... you could launch the app and use a setTimeout to delay the start of processing. The other option is to modify the service after it's created. That's not an out-of-the-box feature though, so you'd have to code that yourself.
@Taximan - pkg is an alternative to node-windows, not an add-on. If you want a real installer, you should look into something like NSIS or another desktop installer.
I want to know how to make the Windows service running with a UI
Is there anyone can help me?please.
I'm interested in providing some more edits, but wanted to start with these two.
e.g., some docs updates, switch from
optimize to minimist, standardize on booleans over 'y/n', etc.
^anyone got any ideas ?
@stokedbits - no TS. Someone may have done it, but if they did, they never told me.
@nabeards - thanks! I've been swamped and my backlog for PR reviews is pretty big. I've pinged one of the other maintainers, but if you don't hear anything, let me know.
@crathermel - node-windows uses winsw behind the scenes. Using nssm is redundant. I believe there is a StackOverflow answer about this.
Maybe a dumb question, I develop on a mac and have a service install script that works with node-mac, I want to develop this installer for windows and will do a process check for the system its running on to use require('node-mac') or require('node-windows') for the environment, but I cant add node-windows to my node-modules to package the electron app because im on a mac. Is there a workaround?
@nburns217_twitter I don't know if you ever got an answer to this. It's unlikely you'll be able to package both versions in a single electron build. In my electron apps, I have a separate build process for mac and windows, which changes the dependency (node-mac vs node-windows) at build time.
Is there anyone who faces this problem?
@coreybutler I have used node-windows in some passion projects of late and would like to make some changes. I noticed you were looking for maintainers, so wanted to learn more to figure out if I could help; and the process (testing / linting needs before a PR may be submitted, etc.). Is there a document somewhere, or some way of looking at pending PRs so I don't attempt a problem that has already been solved, but awaiting a pull.
@AshishShanker - I'd love the help. I don't have a document anywhere (shame on me), but the only real mandate is to make sure the API stays in sync with node-mac and node-linux. Any new features need to be added to all 3 libraries and follow semver. If there are PR's with some new Windows-specific functionality, then I like to weigh in before a change is approved. The goal of the 3 projects are to provide API consistency across all operating systems. I'm trying to avoid what happens in the Electron world where there are some API's that are specific to an OS, yet the project boasts it is entirely cross-platform.
So, if you're interested, just let me know your github handle.
@coreybutler - I will create an issue first describing the perceived shortcoming and outline a potential solution. Then after relevant folks have weighed in, I will code it up and raise a PR. Does that sound like a fair process?