Map metad port to 9559 default

[Dragonchu]

Sorry for my English. I want to do some projects based on nebula meta data. It would be much more convenient if nebulagraph-docker-extension can open port 9559 by default.

[wey-gu]

You just would like to fetch schema with mclient? Or you will need storages client to scan data too?

If it's the case to scan data, run your code in containers with same container network of the extension is much easier.

[Dragonchu]

You just would like to fetch schema with mclient? Or you will need storages client to scan data too?

I just want to fetch schema with mclient. I am trying to convert the nebula schema to graphql schema.

If it's the case to scan data, run your code in containers with same container network of the extension is much easier.

Thanks for the suggestion, I will try this approach. For now I want to develop as fast as possible and reduce dependency on other tools, I currently use docker container ls to see which port the metad is mapped to and then specify it in my tests.

[wey-gu]

You just put your dev container with network:weygu_nebulagraph-dd-ext-desktop-extension_nebula-net, it then could access to the cluster with their container name as host like metad0:9559 :)

[wey-gu]

" I currently use docker container ls to see which port the metad is mapped to and then specify it in my tests." indeed, now it's the easiest way to do so but we are suffering from the exposed address floating from each restart.

I am thinking of leaving only one meta in the cluster and exposing its 9559 port in upcoming releases.