trigger cmd on arch linux

Russ

@Terry-King, no GUI when you run it that way.

You have to edit the ~/.TRIGGERcmdData/commands.json file to add commands.

Terry King

@Russ is there a video that shows how to do this?

Russ

@Terry-King, no, but that's a good idea. I'll work on that - hopefully tomorrow.

EDIT: It's done: https://youtu.be/Iv6ifjHyWF4

Tiago Mártires

Thank Russ for this , but on arch how I run the triggercmd on boot?
my goal is wakeonlan....

thankyuo

Russ

@Tiago-Mártires, I answered here: https://www.triggercmd.com/forum/topic/625/boot-on-arch

mayron

@Russ said in trigger cmd on arch linux:

git clone https://github.com/rvmey/TRIGGERcmd-Agent.git

Sorry to open again this topic, but when i call 'npm install' this error showed and close the build:

npm ERR! notsup Unsupported platform for node-windows@0.1.14: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    win32
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

I think strange, because, the win32 appear... but i use manjaro..

Russ

@mayron, thanks for reporting this.

The package.json that's in-place now might be the windows version. Please try copying the ubuntupackage.json or redhatpackage.json file over-top of package.json like this:

cp ubuntupackage.json package.json

Then try npm install again.

I don't have time right this minute to test it. I'll add a archbuild.sh file to that repo once I know which package.json works.

mayron

@Russ thanks for the answer, now it made the correct build, but i remember that in ubuntu request for the token when I call the command .. here's the message below

$ node ./src/agent.js --console
Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot
Daemon install: false
No token exists.  Login to request one.
prompt: token:  (node:369045) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

Russ

@mayron and I talked over chat and it's working for him now. I tested it too. We just had to press enter at that Warning prompt, then paste in the token. I'll try to get rid of that warning, but at least it works as-is.

I think one of the packages was updated to the latest version which introduced that warning message.

mayron

@Russ thanks!