Remove duplicate main script / entry point

[marc-portier]

Currently there is node launcher.js and node mngr.js ->> this should become one, and documented.

[karel1980]

I'm ok with having both. For development having a quick launch-comm is much handier than having to go via the manager (rest / webapp) to quickly and repeatedly setting up comms.

[karel1980]

Assigned to 0.9. Move the launch-comm script under dev/misc/tools and document it for now as the 'developer' way of launching comms

[karel1980]

Closed by accident

[marc-portier]

The point is that the launcher is designed (maybe needs to changes) to just support that use case.
By adding an extra parameter you can select a certain (test-focussed) config to be used.
Without that extra cli argument it uses config/launcher/me.json

So what I really like to say with this issue is:

• having "persistent" comms to be able to fire up at launch is useful in the final thing too?
• let's agree on how to adapt the config to hold all we need to setup of all to be launched services
• let's make sure we use the full stack in all dev test cases as soon as possible - making sure we enforce convergence between devs sooner rather then later
• me.json should probably be removed from the repo and should be where each instance persists his own set of -gathered service descriptions, -comms you might want to have up and running after each restart
• maybe we should allow the mngr to implement a "save" button to persist the current state into me.json to have available at next launch

[karel1980]

I'm currently working towards this. Depending on how much time I have and how fast it progresses I may split it up in more tasks

[karel1980]

Mngr.js is now called scratchnet.js. The other one is moved under dev-scripts. I am pretty close to eliminating The need for the other one

[karel1980]

See 069c0cd. We don't do persistent comms yet, but it's dead easy to start 2 instances locally and connect them directly.

Note: you can start a single manager and have it create a link with 2 comms (nodejs scratchnet 2000:2000:chat-1.0), but you can't yet have a link with a single comm looping back on itself)

[marc-portier]

Just to clarify & make sure we understand the same thing:

• the described loopback to your own local comm is possible (in the comm)
• but there is currently no easy way to do that in the mngr-ui

right?

[karel1980]

That's right

Marc Portier [email protected]:

Just to clarify & make sure we understand the same thing:

• the described loopback to your own local comm is possible (in the comm)
• but there is currently no easy way to do that in the mngr-ui

right?

Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-36425477.