edgehog
edgehog copied to clipboard
edgehog-device-manager
Easily manage your IoT device fleet with Edgehog at once. Get information on device status, deploy updates, geolocate your devices and much more!
This is something we initially did to have different descriptions for the two queries, but now the description can be passed [inline](https://hexdocs.pm/ash_graphql/dsl-ashgraphql-resource.html#graphql-queries-get-description), and `get? true` doesn't really have any effect...
When paired with an instance of the [Device Forwarder](https://github.com/edgehog-device-manager/edgehog_device_forwarder), Edgehog supports forwarding functionalities that allow direct cloud-device communication. This PR adds the needed configuration in the docker-compose.yml file to enable...
- add missing action buttons and sort them in order of: `Update`, `Reset`, `Delete` - track field changes and enable/disable action buttons (`Update` and `Reset` buttons are enabled when form...
When creating or updating Update Channels, at least one target Device Group must be specified currently. However, it may happen that a user wants to leave an update channel without...
Ash 3.0 introduced the possibility of defining code interfaces at the domain level. We need to decide if we want to have `Domain.Resource.create!` or `Domain.create_resource!` in our codebase.
Right now `gen-edgehog-jwt` is only able to emit JWTs for the GraphQL API. We need to provide an easy way to generate tokens for the admin API.
The changes contained in https://github.com/edgehog-device-manager/edgehog/pull/422 (and possibly https://github.com/edgehog-device-manager/edgehog/pull/410) were not forward ported from release 0.7 since the contexts were gone. They have to be reimplemented directly in Ash.
We should have a common starting point so we can leverage the migration generator for future migrations
Metadata
Owner
Metadata
Easily manage your IoT device fleet with Edgehog at once. Get information on device status, deploy updates, geolocate your devices and much more!