• 211
  • More

Jot Server Installation and Messenger Settings

Hi @Alexey


Using the tutorial foung here, I have managed to installed the JOT Server and everything work fine on my site, including the Messenger.


Here are the steps I have followed:


1) I have asked the Support team of my Hosting company to install node, npm and forever on my server for me.


Node (v14.18.2), Npm (v6.14.15) and forever 4.0.1 were installed..


2) I have asked them to open the Server port 5443 for me.


3) I created a folder called 'jotserver' and uploaded the Jot Server files to it: Here is its location:


/home/xxxxx/jotserver


4) I edited the Jot Server config file config/config.json like this:


{

"port":5443,

"mode":"",

"log":"log.log",

"domains":["*"],

"transformer":"sockjs",

"root":"/home/xxxxx/ssl",

"cert":"certs/xxxxx_com_xxxxx_xxxxx_xxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.crt", 

"key":"keys/xxxxx_xxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key",

"OFFLINE":0,

"ONLINE":1,

"AWAY":2

}


5) I run:


npm install


6) I run:


forever -w --watchDirectory=/home/xxxxx/ssl/certs/ start app.js


As the forever command above was giving me this error: 'command not found' when i first tried it, I had to run the following command first:


npm install forever -g


It installs forever globally.


In the Messenger App, I set the Server URL for messenger like this:


https://www.xxxxxxxx.com:5443


As already mentionned above, everything works fine on the server (both the Jot Server and the Messenger), I am very happy with the installation I did but I still have some questions due to the messages I received while installing the Jot Server.


A) When I run 'npm install', I received this message:


audited 69 packages in 1.237s


3 packages are looking for funding

 run `npm fund` for details


found 1 critical severity vulnerability

 run `npm audit fix` to fix them, or `npm audit` for details


Questions: 


- Was the npm installed properly?

- Should I run `npm audit fix` or just ignore this message?



B) When I run:


forever -w --watchDirectory=/home/xxxxx/ssl/certs/ start app.js


I received the forllowing message:


warn:  --minUptime not set. Defaulting to: 1000ms

warn:  --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms

info:  Forever processing file: app.js

(node:13106) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

(Use `node --trace-warnings ...` to show where the warning was created)

(node:13106) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency


Questions:


- Was app.js forever started properly? Should I just ignore this message?


Many thanks


Replies (2)
    • Hello!


      You can execute audit fix also, but this step can be skipped. These messages start to appear because of new dependencies in Jot Server. You have new Jot Server version, which is not available yet in github, we also use this version on our UNA.io server, it contains new dependencies of the modules which have some notes, but I think, you don't need to worry about that at present. We will release updated version very soon.

      • Hi Alexey. Thank you so much for the explanation. Both Jot Server and the Messenger are working fine, so I will leave things the way they are and wait for the updated version of the Jot Server. Thanks.

        Not logged in users can't 'Comments Post'.
        OneEagle
        •  ·  Premium
        • 985 views
        2
        1