Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

[Feature Request] Not start server at startup #19

Open
ghost opened this issue May 12, 2016 · 5 comments
Open

[Feature Request] Not start server at startup #19

ghost opened this issue May 12, 2016 · 5 comments

Comments

@ghost
Copy link

ghost commented May 12, 2016

Is it possible to have a option not to start the server at startup? Such that I can toggle it on when i want to play with my friend and turn it off when not needed.

If it's already started on my server it takes like 40% cpu idle (the jar that is) which is twice the amount all the other stuff use combined :-) And after every reboot I forget to stop it...

And did I read it correctly there a rest api/json call, or sometime I can call from my home domoticz to start or stop it? That would be sweet!

@gmemstr
Copy link
Member

gmemstr commented May 12, 2016

You can indeed - see Controlling Your Server on the docs https://nodemc.space/index.php/docs/getting-started I will implement a toggle for this in v6 however.

@ghost
Copy link
Author

ghost commented May 13, 2016

That would be great...

I tried it... with the curl commando's, starting/stopping works sometimes.
The problem seems to that curl is stuck forever waiting, like if the
connection is not closed when finised?

It still works but i can not script it if it hangs waiting for this
commando to be finished never returning to the shell prompt:

curl --request POST 'http://127.0.0.1:3000/startserver' --data 'apikey=APIKEYHERE'

but the option would be very nice, no need for script :-)

@ghost
Copy link
Author

ghost commented May 13, 2016

after 10 minutes

curl: (52) Empty reply from server

On Thu, May 12, 2016 at 3:25 PM, Gabriel Simmer [email protected]
wrote:

You can indeed - see Controlling Your Server on the docs
https://nodemc.space/index.php/docs/getting-started I will implement a
toggle for this in v6 however.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#19 (comment)

@gmemstr
Copy link
Member

gmemstr commented May 13, 2016

Will look into this, thanks.

@jaredallard
Copy link
Collaborator

jaredallard commented May 13, 2016

If thats master branch it never uses res to respond back over the TCP
socket (fixed in v6)

@mdcfe mdcfe added this to the v6 milestone May 14, 2016
@mdcfe mdcfe removed the ready label Oct 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants