TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    trigger cmd on arch linux

    General Discussion
    4
    19
    1.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Terry KingT
      Terry King
      last edited by

      is there a way to get trigger cmd running on arch linux? i see there is a linux agent however .deb is debian based distros and rpm i beleive is what ever fedora is based on. i use manjaro which is arch linux with a noob friendly installion (lol) and uses pacman to install which does not allow for the installion of .rpm or .deb files
      any help would be appreciated.

      RussR 2 Replies Last reply Reply Quote 0
      • RussR
        Russ @Terry King
        last edited by

        Hey @Terry-King, I'll look into it.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • RussR
          Russ @Terry King
          last edited by

          @Terry-King, I'm not planning to make an archlinux package, but you could install the agent from the Github repo like this:

          pacman -Sy
          pacman -S nodejs npm git
          git clone https://github.com/rvmey/TRIGGERcmd-Agent.git
          cd TRIGGERcmd-Agent
          npm install
          node ./src/agent.js --console
          

          Russell VanderMey

          Terry KingT 1 Reply Last reply Reply Quote 0
          • Terry KingT
            Terry King @Russ
            last edited by

            @Russ will it work as well as on windows?

            Terry KingT 1 Reply Last reply Reply Quote 0
            • Terry KingT
              Terry King @Terry King
              last edited by Terry King

              @Russ here is a recording of my terminal output when i run those commands https://asciinema.org/a/xxStYX1LqovlHqvpDsf3vuY6G

              RussR 1 Reply Last reply Reply Quote 0
              • RussR
                Russ @Terry King
                last edited by Russ

                @Terry-King, you were close. You can generally ignore those warnings when you run npm install. So you probably just had to run this when you were in the TRIGGERcmd-Agent folder:

                node ./src/agent.js --console
                

                You're not running X Windows right? That command runs the agent in forground mode and doesn't give you the tray icon or the GUI command editor, so you'll have to edit your ~/.TRIGGERcmdData/commands.json file with a text editor.

                Russell VanderMey

                Terry KingT 1 Reply Last reply Reply Quote 0
                • Terry KingT
                  Terry King @Russ
                  last edited by

                  @Russ uhm i honestly dont know. here is my neofetch if that helps link text

                  RussR 1 Reply Last reply Reply Quote 0
                  • RussR
                    Russ @Terry King
                    last edited by

                    @Terry-King, I think it will work if you try again, and just run this command:

                    node ./src/agent.js --console
                    

                    Russell VanderMey

                    1 Reply Last reply Reply Quote 0
                    • Terry KingT
                      Terry King
                      last edited by

                      ok i got the app installed (it asked me for my token) but there isnt a GUI? how do i set up commands?

                      RussR 1 Reply Last reply Reply Quote 0
                      • RussR
                        Russ @Terry King
                        last edited by Russ

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

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

                        Russell VanderMey

                        Terry KingT 1 Reply Last reply Reply Quote 0
                        • Terry KingT
                          Terry King @Russ
                          last edited by

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

                          RussR 1 Reply Last reply Reply Quote 0
                          • RussR
                            Russ @Terry King
                            last edited by 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

                            Russell VanderMey

                            1 Reply Last reply Reply Quote 0
                            • Tiago MártiresT
                              Tiago Mártires
                              last edited by

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

                              thankyuo

                              RussR 1 Reply Last reply Reply Quote 0
                              • RussR
                                Russ @Tiago Mártires
                                last edited by

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

                                Russell VanderMey

                                1 Reply Last reply Reply Quote 0
                                • M
                                  mayron
                                  last edited by 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..

                                  RussR 1 Reply Last reply Reply Quote 0
                                  • RussR
                                    Russ @mayron
                                    last edited by

                                    @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.

                                    Russell VanderMey

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      mayron @Russ
                                      last edited by 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
                                      
                                      
                                      RussR 1 Reply Last reply Reply Quote 0
                                      • RussR
                                        Russ @mayron
                                        last edited by

                                        @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.

                                        Russell VanderMey

                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          mayron @Russ
                                          last edited by

                                          @Russ thanks!

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post