-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add example User Interface #23
Comments
michelleFranke
added a commit
to sotec-iot/hono-extras
that referenced
this issue
Apr 24, 2023
At this PR we have created an example user interface for a Google Cloud based deployment. The UI is able to communicate with the Device Registry API and the Device Communication API. - Added new module to support a user interface based on Angular 15 - Added components for tenants, devices, credentials, configs and states - Added services for communicating with the APIs - Added Dockerfile - Updated Readme Signed-off-by: michelle <[email protected]>
julian-sotec
pushed a commit
to sotec-iot/hono-extras
that referenced
this issue
Aug 8, 2023
At this PR we have created an example user interface for a Google Cloud based deployment. The UI is able to communicate with the Device Registry API and the Device Communication API. - Added new module to support a user interface based on Angular 15 - Added components for tenants, devices, credentials, configs and states - Added services for communicating with the APIs - Added Dockerfile - Updated Readme Signed-off-by: michelle <[email protected]>
calohmn
pushed a commit
that referenced
this issue
Nov 4, 2023
At this PR we have created an example user interface for a Google Cloud based deployment. The UI is able to communicate with the Device Registry API and the Device Communication API. - Added new module to support a user interface based on Angular 15 - Added components for tenants, devices, credentials, configs and states - Added services for communicating with the APIs - Added Dockerfile - Updated Readme - Added request/response command capability --------- Signed-off-by: michelle <[email protected]> Signed-off-by: patrick <[email protected]> Signed-off-by: Muhammed <[email protected]> Signed-off-by: Matthias Kaemmer <[email protected]> Signed-off-by: g.dimitropoulos <[email protected]> Signed-off-by: Hoang Sa Nguyen <[email protected]> Signed-off-by: julian <[email protected]> Co-authored-by: patrick <[email protected]> Co-authored-by: Muhammed <[email protected]> Co-authored-by: g.dimitropoulos <[email protected]> Co-authored-by: Hoang Sa Nguyen <[email protected]> Co-authored-by: julian <[email protected]>
This was referenced Nov 4, 2023
calohmn
added a commit
that referenced
this issue
Nov 13, 2023
This reverts commit b2216e5. The changes from that commit shall be applied again in the form of multiple commits.
calohmn
pushed a commit
that referenced
this issue
Nov 18, 2023
At this PR we have created an example user interface for a Google Cloud based deployment. The UI is able to communicate with the Device Registry API and the Device Communication API. - Added new module to support a user interface based on Angular 15 - Added components for tenants, devices, credentials, configs and states - Added services for communicating with the APIs - Added Dockerfile - Updated Readme Signed-off-by: michelle <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is part of the adaption process in order to qualify Hono as a replacement for Google IoT Core customers. We want to give users the possibility to operate with the Device Registry API as well as with the Device Communication API [#19] with the help of an user interface.
In order to provide an user interface, frontend implementation based on Angular 15 has been made. This example implementation provides frontend functionality for a Google Cloud based deployment. We are recommending using IAP for your API security. Make sure to configure your OAuth consent screen. This UI will provide the possibility to:
1. Access the Device Registry API containing actions like:
2. Access the Device Communication API containing actions like:
Note: This UI cannot be run without further adjustments! If one wants to use this UI in other environments than on Google Cloud, adjustments have to be made to not include the GoogleService and to update the url suffixes of the services. One consideration is to adjust the environment files in the future.
The text was updated successfully, but these errors were encountered: