Swordsteel
119d14eb46
- add NodesController - add NodesEndpoint - add NodesControllerTest - add NodesController - add nodes.http - add NodeEntity toNodesResponse in Mapping.kt - add getNodes to NodeService - add findAll to NodeRepository
Hlæja Device Register
Classes crafted, identities bestowed, Each device recorded, their functions unfold. From sensors to systems, connections take shape, A registry formed, no detail escapes. Signals exchanged, precision is key, Each device declared, its purpose set free. The Device Register, steadfast and true, A harmony of devices, perfectly aligned.
Properties for deployment
| name | required | info |
|---|---|---|
| spring.profiles.active | ✓ | Spring Boot environment |
| spring.r2dbc.url | ✓ | Postgres host url |
| spring.r2dbc.username | ✓ | Postgres username |
| spring.r2dbc.password | ✗ | Postgres password |
| jwt.private-key | ✓ | JWT private cert |
Required: ✓ can be stored as text, and ✗ need to be stored as secret.
Releasing Service
Run release pipeline from master branch.
Development Information
Private RSA Key
This service uses RAS keys to create identities for devices. The private key is used here to generate identities, while the public key is used by Hlæja Device API to identify a device and accept data.
For instructions on how to set these up, please refer to our generate RSA key documentation.
Global Setting
The following global settings are used in Hlaeja Device Registry. You can configure these settings using either Gradle properties or alternatively environment variables.
For instructions on how to set these up, please refer to our set global settings documentation.
Gradle Properties
repository.user=your_user
repository.token=your_token_value
Environment Variables
REPOSITORY_USER=your_user
REPOSITORY_TOKEN=your_token_value