App Platform -- Static IP
We should be able to securely whitelist our infrastructure to access external resources, without apps being able to be given static IP addresses we can not use the service without opening our infrastructure to security problems.
Support Node.js 18 in App Platform
The App Platform only supports up to Node 17 which is no longer receives support updates and is not recommended for production systems. Please update the Node.js buildpack to support Node 18.
Automatic horizontal scaling
This is really a must have function for the app platform. Is there any ETA when this will be available?
VPC with Apps, Droplets and Managed Databases
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.
Notifications to include resource name
Although I like the notifications (on Slack) when a deployment has failed or been successful, it doesn't include the resource name that has been deployed. Could this be added to the notification, in addition to only the overall App name.
Sticky Sessions for App Platform
Add the possibility to configure session affinity in the app plataform web services. It is use for some applications which use websockets.
Sticky sessions for App Platform
Allow the App Platform load balancer to support sticky sessions. We need this for horizontally scaling with socket.io 's long polling transport.
Same domain for multiple Apps
Currently it is not possible to assign the same subdomain to 2 apps. It would really help to setup a Geolocation DNS routing and have multi-region Apps.
Multiple App Deployments
It would be nice to be able to set up multiple deployments from different branches (for example main and develop, feature branches and even tags) or different image tags.A possible way to do this could be to create the concept of "sub-apps" or "app slots". The main app would be the production one; if there's a web deployment, it would be the one using the domain name as now.Each "sub-app" or "slot" could be(1) manually created, using a different branch or image tag; if there's a web deployment it would prepend a subdomain to the main app domain or(2) automatically created, everytime a branch or git tag is committed; if there's a web deployment, there are two alternatives (2.1) domain is managed by DO, therefore, we can automatically add the subdomain, just like the previous or the main or (2.1) domain is managed externally, so we add the subdomain only for the DO default domain only, which is probably fine if it's for internal use (previews).In addition, it would be nice to be able to "promote" a deployment from "sub-app" or "app slot" into the main app.