Define how Connectors and Adverisments are announced and stored in Datum Cloud #26
Description
There will be APIs to post and read the Connector and Advertisment resources, which will replace the iroh-n0des ticket based system that is in the codebase at the moment.
-
AFAIU proxies will be stored as connector + advertisment within a Project in the Datum Cloud.
-
Technically, running these proxies is tightly coupled to a device, a single instance of the Datum Connect app, identified by its iroh endpoint id.
-
One approach would be to make proxies local-first, i.e. whenever the datum-connect app is started, it uses its local state and pushes that to Datum Cloud, replacing the previous state for this device (i.e. removing all previous connectors + advertisments for this device).
-
Managing proxies over Datum Cloud more directly would also be possible, however we have to properly evaluate what that would mean - i.e. it would likely be unwelcome if another project member edited a proxy running on my laptop and thus exposing a port without me knowing about that.