TCP App Platform (non-web service)
Nathanial Howard
Very similar to the current offering on the App Platform. I would love to have some code (in my case, C++) deploy via App Platform, but NOT behind a CloudFlare CDN/Proxy ip and NOT HTTPS-only.
I would love to host an app that uses TCP sockets and NOT HTTP.
Yes, I can deploy to it (I tested this out with a Dockerfile repo), but it's not usable in reality because there is no static ipv4 publicly accessible.
Current working implementation/alternative is to use a Droplet with Docker installed, and set up containrrr/watchtower, and push from github -> github actions -> DO Container Registry -> watchtower updates my container for me with the latest image every X seconds (configurable) But, obviously that's a bit clunky. No clean way to provide environment variables that I know of (Maybe I need to learn more about Docker for this step)
Anyone have similar needs?
T
Tamas Kalman
I wasn't even aware that i can't run a TCP only service on DO. Is this still something unsupported in 2023?
Johyn Papin
This would allow us to deploy our gRPC services on App Platform, which would be really cool for us.
G
Goncalo Oliveira
This is something that I've asked before, though can't find the post anymore, probably archived.
There's definitely value in having more than just HTTP/S Apps. Understandably it's not everyone's cup of tea, as most Apps are web apps, but there are a variety of scenarios for Apps that require direct TCP connections.
Something else that's worth mentioning is that sometimes one might need mixed content (multiple ports)... Thinking about a particular service we have that listens to HTTP content on one port (REST server) and TCP content on another port.
It's not hard to do, I think, although it will probably require allocating a dedicated IP to an App.
Unfortunately for these scenarios we ended up using something else (offered by a different provider).
Would be nice to have someone from DO commenting on this.
He He
Heng