Closed rmg closed 9 years ago
Needs linting.
@rmg I'll drop 447cce7, its not needed, but we have to sort out what happens when pm is run consecutively with different driver types.
@sam-github it still lacks useful tests, but it's lint free and works for all my manual testing cases, so I think you can start reviewing now.
Looks pretty good. The code is quite easy to follow, except for the instance juggling.
I've only read through the driver, I'll try to get through container and image tonight.
Could you get it running on ubuntu, so that I can do a bit of functional testing/trying it out?
Appears to be running, but I can't curl the port that meshctl says is being listened on. docker inspect seems to imply the image is on port 3000, but I can't curl that, either.
Basically LGTM other than a couple nits. And that I can't reach my apps that meshctl says are listening. I could use a docker tutorial, I think.
@sam-github would you like me to remove the new listening
event I added? All it does is allow the PM logs to show sl-pm: Service "1" listening on 0.0.0.0:3001
Oh ya, I remember... the listening
event and that filtering were both added in #194
slc ctl set-size 1 N
handle instance containers already running when PM startsstarted
notificationdirect
vs.docker
Tests
Connect to strongloop-internal/scrum-nodeops#402 Connect to strongloop-internal/scrum-nodeops#484