-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Api (Server) #2
Comments
npm install -g nodemon server listening on http://0.0.0.0:5555
Read READYheater -do stop
[Error: ENOENT: no such file or directory, open '/tmp/shairport-sync-metadata'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/tmp/shairport-sync-metadata'
}
[nodemon] app crashed - waiting for file changes before starting... After install That server is startet but crashed. |
Thank's for your issue. I could reproduce the bug and fixed it with the latest changes. Hope it works for you? |
Next Crash /home/punky/develop/herbiOS/api/src/lights/LightsService.ts:21
for (const lightConfiguration of this.config.get().lights) {
^
TypeError: this.config.get.lights is not iterable
at new LightsService (/home/punky/develop/herbiOS/api/src/lights/LightsService.ts:21:59)
at Function.getInstance (/home/punky/develop/herbiOS/api/src/lights/LightsService.ts:12:35)
at LightsSocket._socket (/home/punky/develop/herbiOS/api/src/lights/LightsSocket.ts:31:45)
at Namespace.<anonymous> (/home/punky/develop/herbiOS/api/src/api/websocket/NamespaceSocket.ts:59:18)
at Namespace.emit (events.js:400:28)
at Namespace.emit (domain.js:470:12)
at Namespace.emitReserved (/home/punky/develop/herbiOS/api/node_modules/socket.io/dist/typed-events.js:56:22)
at /home/punky/develop/herbiOS/api/node_modules/socket.io/dist/namespace.js:141:26
at processTicksAndRejections (internal/process/task_queues.js:77:11) Question: |
This is caused because there is no update path at the moment. The server generates configuration files in the You can modify the configurations for your needs. Add lights in the The I will add this to the readme. |
Can not Start the Backend Server
The text was updated successfully, but these errors were encountered: