[Feature Request] Multi Server Support

[Anton C. Swartz IV]

What is the possibility of adding in functionality to allow one to have multiple servers. While one could spin up an instance for each server you are effectively doubling port usage. .

[Gabriel Simmer]

Will consider this, thank you.

[MD]

This could be achieved in v5 with plugin magic, although it would still require spinning up another NodeMC instance. In v6, it's likely that this will be much easier to do (either natively or with a plugin).

[Jared Allard]

This could be a cool idea for seperating servers into daemons. TL;DR: separation of child_process into a daemon. I did something like this in https://github.com/rdelrod/mcfd. It'd also allow servers to stay up if the backend were to ever crash.

Actually, this is probably a good idea to implement to separate the processes.

[MD]

Oops, was supposed to be v7.

[MD]

@jaredallard We could either fork the process or spawn a completely separate process - the issue being that then we need to be able to handle multiple potentially spammy logs (many plugins love to write to the console multiple times per tick if they feel like it) and also maintain IPC links to each of them.

[Jared Allard]

Could easily write a wrapper to use socket.io or just webhooks to interact
with a daemon for it.

On Thu, Jun 2, 2016 at 1:32 PM Mathew Da Costa [e-mail]
wrote:

@jaredallard https://github.com/jaredallard We could either fork the
process or spawn a completely separate process - the issue being that then
we need to be able to handle multiple potentially spammy logs (many plugins
love to write to the console multiple times per tick if they feel like it)
and also maintain IPC links to each of them.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACR9NS9pgn8BIsWYxPdNac83NLZixj-eks5qHz3mgaJpZM4H0efj
.

[MD]

@jaredallard We could, but by that point we might as well write a wrapper to tie together multiple NodeMC instances.

[Jared Allard]

Yeah, it was just a thought.

On Thu, Jun 2, 2016, 13:43 Mathew Da Costa [e-mail] wrote:

@jaredallard https://github.com/jaredallard We could, but by that point
we might as well write a wrapper to tie together multiple NodeMC instances

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACR9NXR_OyLhkfqP2Dl-PybsZhRATEmnks5qH0BggaJpZM4H0efj
.