EdgeX Tooling Poll #34
Replies: 4 comments 2 replies
-
Plus our own tooling - so all of the above. |
Beta Was this translation helpful? Give feedback.
-
We use Postman to access all the APIs. We usually run EdgeX on the target machine or the development machine(WSL) and open the ports for access within the network. Then we access the services through API calls using Postman. |
Beta Was this translation helpful? Give feedback.
-
Each method of access is required since each of them cater to different audience: API ( postman collection) is good for developers, CLI is for devOps/QA team while UI is for end users/customers. I know current UI is not meant for production use, so we have developed our own UI that provides a consolidated view of profile/devices across multiple deployments ( data is synced) |
Beta Was this translation helpful? Give feedback.
-
@JamesKButcher Can you please guide me where can I find the CLI tool for EdgeX? |
Beta Was this translation helpful? Give feedback.
-
Hi EdgeX Community!
I’m looking for some responses from the users of EdgeX as to how they interact with EdgeX please…
Obviously we have well defined APIs for controlling and interfacing with EdgeX. But we also have a Command Line Interface (CLI) and a Graphical User Interface (GUI). I’d like to hear whether people generally use all of the above or whether they focus on using just the APIs and/or create their own tooling. This info will help with our focus going forward.
Looks like we can only select one answer with the poll tool here, hence all my different options below! But please leave any additional info in the comments.
Thanks all,
James Butcher
EdgeX TSC Chair
22 votes ·
Beta Was this translation helpful? Give feedback.
All reactions