1thorsten / ewake Goto Github PK

Installed on multiple host docker environments to verify issue. While host is running if I click any of the options.

show active clients
show internal logs
show ip address and mac address of the requesting host

The host server docker container crashes. Networking is set to Host. Open ports are 5555 --> 5555. -V mapped to /opt/ewake --> /ewake-clients

Docker logs show.

node:internal/errors:497
ErrorCaptureStackTrace(err);
^
Error [ERR_HTTP_HEADERS_SENT]: Cannot write headers after they are sent to the client
at new NodeError (node:internal/errors:406:5)
at ServerResponse.writeHead (node:_http_server:345:11)
at a.httpError (/ewake/ewake.js:2:54010)
at Server. (/ewake/ewake.js:2:259856)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
code: 'ERR_HTTP_HEADERS_SENT'
}
Node.js v20.9.0

Thanks for any help!

In order to enable cluster operation, it should also be possible to access the configuration via HTTP as an alternative to the file system.
Writing requires WebDAV support on the part of the HTTP server.

Tasks:

• argument file should be handle URI as well
• introduce another argument for readonly access to the configuration.
• update the documentation

Currently, the network interface can be passed as an HTTP argument. Accordingly, the transfer is made by the user.
This makes no sense, the network interface is a setting that must apply to the server.

Therefore it should be possible to pass the network interface as an argument (command line) when starting the server. The possibility for the user is to be omitted.

tasks

• add command line argument (-i --interface)
• adjust call to arp (windows, linux, mac)
• show the choosen network interface after starting the server
• adjust documentation

• Dockerfile and docker-compose.yml
• add npm script to build docker image as well
• update README.md to reflect usage with docker
• use environment variables as another possiblity to control the app (use env as default value which can be changed with arguments)
  e.g, control of the server of the server port (--port)

at the moment the default is port 5555. Idea is that the default comes from env.PORT and only when this is not defined take a fixed default value (5555)