You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There had been someone asking me on building nebula-importer step by step w/o knowing that we have binary deliverables for it.
Today someone else queried me again on this and I just realize that in documentation we only mentioned the go build or docker method on using importer.
Actually, we all know that the binary package is much easier to do so, given that the user may not familiar with the docker(what does -v mean to know how the config file and data should be placed inside the docker).
Thus I think we should highlight that it's easier to download the binary package before trying to build it.
There had been someone asking me on building nebula-importer step by step w/o knowing that we have binary deliverables for it.
Today someone else queried me again on this and I just realize that in documentation we only mentioned the go build or docker method on using importer.
Actually, we all know that the binary package is much easier to do so, given that the user may not familiar with the docker(what does
-v
mean to know how the config file and data should be placed inside the docker).Thus I think we should highlight that it's easier to download the binary package before trying to build it.
https://docs.nebula-graph.com.cn/2.6.1/nebula-importer/use-importer/
The text was updated successfully, but these errors were encountered: