I’d like to post some data from a Raspberry Pi to an instance running in DigitalOcean (called droplet at DigitalOcean). Is it possible using Twingate to connect the Raspberry Pi directly to the internal network in which the instance is running in DigitalOcean? I’m investigating another solution than having to make my instance publicly available and configure firewall, inbound rules, port forwarding, reverse proxy…
So far, I’ve deployed a Twingate connector to the droplet (via Docker). The droplet exposes a service on port 3000, which I could well access from my laptop after defining a Twingate Resource pointing to the internal IP of the droplet (where the connector runs) and connecting with the Twingate macOS client.
I don’t see however how to access this same resource from the Raspberry Pi. My understanding is that I would need to install a Twingate client to the Raspberry Pi to do this. Is that correct? From the doc, I see that linux clients are only available for 64-bit architecture, and my Raspberry Pi is running a 32 bit OS…
Is that a supported use case for Twingate?
Thanks in advance