TTN Munich Platform: Difference between revisions
(initial) |
(→Open Points: Databases) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 27: | Line 27: | ||
For the showroom instance, we need to allow anonymous read access, so we had to adapt the LDAP auth plugin a bit: [https://github.com/tiefpunkt/node-red-contrib-ldap-auth/tree/anonymous_read modified code] | For the showroom instance, we need to allow anonymous read access, so we had to adapt the LDAP auth plugin a bit: [https://github.com/tiefpunkt/node-red-contrib-ldap-auth/tree/anonymous_read modified code] | ||
== Open Points == | |||
There are still some things to figure out | |||
=== LDAP Access Control === | |||
We would like to work with LDAP groups, but the NodeRed Plugin does not really support that properly. Need to figure out some options here | |||
* [https://openldap.org/doc/admin24/overlays.html LDAP Overlay on Server side] | |||
Also, we don't have access control on Dashboards right now. | |||
=== Admin Panel === | |||
Management using LAM and SelfService is a little difficult. What other options are out there? | |||
* [https://git.cccv.de/infra/uffd/uffd/ UserFerwaltungsFrontend] by CCCV? | |||
=== Theming === | |||
We could adapt the UI a bit more | |||
* https://github.com/node-red/node-red/issues/610 | |||
* https://nodered.org/docs/user-guide/runtime/configuration#editor-themes | |||
=== Notifications === | |||
We could provide a standardized option for notifications | |||
* SMS? [https://www.sms77.io/] [https://www.clicksend.com/de/pricing/de/] | |||
* Pushbullet [https://www.iotwithus.com/using-pushbullet-to-get-notifications-from-node-red/] | |||
=== Data Storage === | |||
There's currently no database option available on the platform. There are a few ways we could address this | |||
* Different databases | |||
** Time Series (Influx) | |||
** "Traditional" SQL (MariaDB, Postgres, ...) | |||
** NoSQL (MongoDB) | |||
* Integrate with NodeRed into single container, or dedicated container | |||
[[Category:Project]] | [[Category:Project]] | ||
Latest revision as of 09:05, 18 October 2021
| TTN Munich Platform Release status: beta [box doku] | |
|---|---|
| |
| Description | a free LoRaWan Network for Munich |
| Author(s) | Severin, Joe |
We're building a platform to enable development for TTN/LoRaWAN applications.
Architecture
Right now, we're running NodeRed instances, with some central infrastructure around it. All is containerised into individual Docker containers, and currently run on infrastructure provided by Severin. As we get more users, we'll likely migrate it to separate servers.
Central components
- LDAP Server
- LDAP User Management
- Self-Service Account Management
- HTTP(S) Proxy
Node-Red
Custom container base on the original docker image, with the LDAP auth plugin.
For the showroom instance, we need to allow anonymous read access, so we had to adapt the LDAP auth plugin a bit: modified code
Open Points
There are still some things to figure out
LDAP Access Control
We would like to work with LDAP groups, but the NodeRed Plugin does not really support that properly. Need to figure out some options here
Also, we don't have access control on Dashboards right now.
Admin Panel
Management using LAM and SelfService is a little difficult. What other options are out there?
- UserFerwaltungsFrontend by CCCV?
Theming
We could adapt the UI a bit more
- https://github.com/node-red/node-red/issues/610
- https://nodered.org/docs/user-guide/runtime/configuration#editor-themes
Notifications
We could provide a standardized option for notifications
Data Storage
There's currently no database option available on the platform. There are a few ways we could address this
- Different databases
- Time Series (Influx)
- "Traditional" SQL (MariaDB, Postgres, ...)
- NoSQL (MongoDB)
- Integrate with NodeRed into single container, or dedicated container
