NEEO - Driver Manager (ALPHA)

Hi Bruno 

Thanks - it's still some way from being MVP and sharable with the community as outlined in the post above but it's getting there. I'll definitely create an issue on the SDK repo and share a link when its ready, hopefully the NEEO engineering team can pull the parts they like/want lol.

Niels de Klerk Thanks, I hope it turns out to be useful. I haven't been on here very long but I can see that you're very active in the community and are contributing lots towards the drivers and SDK development so I'd love to know how you get on with this and welcome any feedback you have :)

Mike Potts So at the moment it is using a webpack development server which by default doesn't allow remote connections, however you can make one real quick change in the webpack,.config.js file. if you add:

host: '0.0.0.0',

in that config then it will be accessible via your debian vm IP+port. For example: http://192.168.12.50:3000 (assuming you debian vm ip is 192.168.12.50.

Its still beta so in the future I want it to be self contained and require no setup, but its not at that stage yet.

Hope that help.

Mike Potts Replace the section "devServer", with:

devServer: {
    host: '0.0.0.0',
    port: 3000,
    proxy: {
      '/api': {
        'target': 'http://localhost:3001',
        'ws': true
      },
      '/socket.io': {
        'target': 'http://localhost:3001',
        'ws': true
      }
    },
    compress: true,
    historyApiFallback: true,
    open: true,
    // hot: true, // hot module replacement. Depends on HotModuleReplacementPlugin
  }

I just tried that here and it's working for me remotely. If that doesn't work then can you post a screenshot of what you're are seeing?

Mike Potts If you pull down the latest code I've updated it so it should work remotely without you needing to change any config. Let me know if it works.

Mike Potts At the moment you have to manually add them by searching NPM, once installed the manager will auto start them. If they fail to run (nothing to do with the manager) then it will show as errored. So if you have some drivers already running it won't recognise them, you will need to stop the existing driver servers you already have running and then add them through the manager (providing the person that built them has published them to NPM).

It is limited at the moment but it is a start. After speaking with the SDK devs it looks like some useful driver management stuff is coming into the the next release of the SDK via a command line. When that is released I might be able to tap into it a bit more for things like discovery of drivers etc.

I would recommend pulling down my latest changes as it adds another fix in there for the websocket connection for real time GUI updates.

Mike Potts no worries, just follow what the video does. Hopefully that does a better job of explaining then my words!

Niels de Klerk Thanks so much for trying it out and providing some feedback. Would it possible for you to raise these issues against the GitHub repo so I can keep track of them and take a look for you? Thanks again, much appreciated :)

Niels de Klerk Ace. Thanks so much. I just triaged them and I will have a fix up for the 4 bugs in ~5 mins. Just testing it now. The search UX is much nicer now too.

Niels de Klerk All fixed bud, also got a way nicer search UX going on:

Please pull the latest code.