App Platform

At the time of writing Functions are unable to make use of App Platform's internal routing, meaning they cannot call other components in the same App Platform they're in. This limitation means there is little value of having Functions inside an App Platform as they do not enjoy the same abilities other components have by making use of internal routing. Please consider making it possible for Functions to make use of internal routing inside App Platform.

Please allow app platform apps to use block storage volumes and not just spaces for permanent storage that is not erased when app is re-deployed.

Being able to integrate Apps into a VPC together with droplets and managed databases, would allow secure / private access to them. Maybe even kubernetes could be integrated.

For example, a Django app can run on the apex domain, a web service on 'api.', and a static wiki on 'docs.'

It would be great if we could use cloud firewalls to control access to deployed applications using App Platform. I've got some private applications that I would deploy using your PaaS offering immediately if I could firewall it off.

I'm trying to serve Server-Sent Events (SSE) using Flask on the DO App Platform, but instead of streaming, something on DO's side seems to be caching the entire response and only returning it in one big chunk. I've been trying and trying to debug, and finally found this page which seems to indicate it's not possible? https://www.digitalocean.com/community/questions/how-to-enable-http-response-streaming-in-the-app-platform So I have to migrate off the app platform now I guess? Or am I missing something?

The Apps spec only permits registry types of DOCR and DOCKER_HUB.It would be useful to permit additional registries including GitHub Container Registry (GHCR) and Google Container Registry.I assume this limitation is partly due to [DO] cost but, without it, the developer incurs the costs in potentially managing duplicate images across registries.

Add the possibility to configure session affinity in the app plataform web services. It is use for some applications which use websockets.

The interface defaults to the browser's language, and for multilingual users that's useless, because it's always better to read the messages in their original language to avoid errors.

Sometimes when containers are restarted automatically, is not clear why that's the case. It could be a spike in CPU usage, being out of memory or storage, etc. I have experienced situations where it's not that clear what the reason is and the crash logs (via doctl and via UI) only says that the "container was terminated", difficulting finding a solution to the issue.