josephdadams / midi-relay

Listens for HTTP request with JSON payload and relays MIDI/MSC commands on local ports.
MIT License
58 stars 9 forks source link

Installation of midi-relay (as a service) on a RPi #16

Closed mark-epstein closed 3 years ago

mark-epstein commented 3 years ago


Tried to do a manual install of Companion on my new rpi, got to some error message I couldn't understand and Google didn't help, so I started over with a CompanionPi image.  On my own, etc, I get it but Companion seems to be running OK.

Next I wanted to add midi-relay.  Installed node I think successfully, I get this:
```
    pi@raspberrypi:/usr/local/src/midi-relay/midi-relay-2.2.0 $ node --version
    v15.12.0

```
But if I try to run **sudo npm install -g pm2** I get this response:
```
    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss                   ues/797)
    /usr/local/bin/pm2 -> /usr/local/lib/node_modules/pm2/bin/pm2
    /usr/local/bin/pm2-dev -> /usr/local/lib/node_modules/pm2/bin/pm2-dev
    /usr/local/bin/pm2-docker -> /usr/local/lib/node_modules/pm2/bin/pm2-docker
    /usr/local/bin/pm2-runtime -> /usr/local/lib/node_modules/pm2/bin/pm2-runtime
    npm WARN notsup Unsupported engine for mkdirp@1.0.4: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
    npm WARN notsup Not compatible with your version of node/npm: mkdirp@1.0.4
    npm WARN notsup Unsupported engine for semver@7.3.5: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
    npm WARN notsup Not compatible with your version of node/npm: semver@7.3.5
    npm WARN notsup Unsupported engine for semver@7.2.3: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
    npm WARN notsup Not compatible with your version of node/npm: semver@7.2.3
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/pm2/node_modules/chokidar/node_modules/fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}                   )
    npm WARN notsup Unsupported engine for escape-string-regexp@4.0.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
    npm WARN notsup Not compatible with your version of node/npm: escape-string-regexp@4.0.0
    npm WARN notsup Unsupported engine for lru-cache@6.0.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
    npm WARN notsup Not compatible with your version of node/npm: lru-cache@6.0.0

    + pm2@4.5.5
    updated 1 package in 10.66s

```
I don't understand why these errors seem insistent that I'm running node v8.17.0 when node itself tells me I'm running 15.12.0.  Am I misinterpreting the messages?

Also my npm version is 7.6.3 (not 6.13.4)
And midi-relay runs under Node manually, (at least it appears to, I haven't tested any actual MIDI transport) but I'd like it to run as a service.
mark-epstein commented 3 years ago

I feel like MY learning linux is like learning to ride a bicycle on the side of a motorcyle race track. When I do something wrong, I rarely know what I did. Same as when I do something right.

I don't know what I did but somehow the same command is no longer giving me those "notsup" warnings and everything is running. ¯\(ツ)