Skip to content

npm port option not taken into account #68

@Pulsar2011

Description

@Pulsar2011

I am trying to have ICARUS working on Linux following your instruction.
I have a docker running some local grafanan server which are listening to port 3300, same as ICARUS, therefore, I explicitly define on which port ICARUS should listen with -p option. But this doesn't seems to be taken into account :

npm start -p 4600

icarus@0.22.0 start
npm run dev 4600

icarus@0.22.0 dev
node src/service/main.js --dev 4600

ICARUS Terminal Service 0.22.0
Loading save game data from /Users/gillard/Library/Containers/com.isaacmarovitz.Whisky/Bottles/C096BC61-AB61-420D-B7A2-00738244E801/drive_c/users/crossover/Saved Games/Frontier Developments/Elite Dangerous/
Listening on port 3300…
Scanned 27 files
Imported 3622 events

I also tryed directly change the port to listen into the script itself, changing line 37 in main.js. If I do so, the "Listening to port" is now correctly set with the desired value but when I now access the page on a browser, I got an error message :

(node:48035) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
(Use node --trace-deprecation ... to show where the warning was created)

And strangely, my browser is forwarded to the front page of th grafana running on my docker.

First, could you see why the port number is not properly tacken into account when specified in command line.

Why I end up on the docker grafana webpage when accessing the ICARUS client with a different port number from the one used by the docker ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions