hi @Adurm
That depends on the type of app. If it is an integration you need to run the NodeJS part on an Internet connected server. For (board)views you can upload the app to monday.
bummer… i thought that would be the case.
I uploaded it to an external server, but unfortunately something doesnt transfer across from the quickstart integration setup as it fails to deploy with the error:
"2022-09-28 05:28:32] node:events:491
>2022-09-28 05:28:32] throw er; // Unhandled 'error' event
>2022-09-28 05:28:32] ^
>2022-09-28 05:28:32]
>2022-09-28 05:28:32] Error: spawn lsof ENOENT
>2022-09-28 05:28:32] at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
>2022-09-28 05:28:32] at onErrorNT (node:internal/child_process:478:16)
>2022-09-28 05:28:32] at processTicksAndRejections (node:internal/process/task_queues:83:21)
>2022-09-28 05:28:32] Emitted 'error' event on ChildProcess instance at:
>2022-09-28 05:28:32] at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
>2022-09-28 05:28:32] at onErrorNT (node:internal/child_process:478:16)
>2022-09-28 05:28:32] at processTicksAndRejections (node:internal/process/task_queues:83:21) {
>2022-09-28 05:28:32] errno: -2,
>2022-09-28 05:28:32] code: 'ENOENT',
>2022-09-28 05:28:32] syscall: 'spawn lsof',
>2022-09-28 05:28:32] path: 'lsof',
>2022-09-28 05:28:32] spawnargs: : '-s', 'TCP:LISTEN', '-i', ':8302' ]
>2022-09-28 05:28:32] }
I’ve had the same issue while using Docker to run the app.
To resolve this I’ve removed the kill-port command from the “stop” within package.json:
{
"name": "monday-integration-quickstart",
"version": "0.0.1",
"license": "MIT",
"scripts": {
"start": "npm run stop && npm run server",
"server": "nodemon ./src/app.js",
"stop" : ""
},