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 for Gzip for static sites would be great to speed things up even further. Thanks!
Delete with 24 hour cooldown
We run our production database using DO's managed postgres. Because we are a devops team, quite a few people have access to our DO login. It's very easy at the moment to just delete the production database without it being recoverable (it's just a button and dialog). As owner, I want to have some sort of feature flag that I can say: 'if someone wants to delete database X, only do that 24 hours from now, and send an warning email that this will happen to X email adres.' This way, if it happens by a malicious user, we can take action, before we lose all our data. I think this should be an option I can turn on / off only once a week (for security purposes) and that, because I enable the option, I have to pay the 24 hours the DB is still recoverable after deletion.
Automatic horizontal scaling
This is really a must have function for the app platform. Is there any ETA when this will be available?
Support for Docker images to Functions
I think serverless functions should support a built executable artifacts or entire container images instead of requiring source code.
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.
Add support to configure CRON job
We are looking for sending scheduled updates to the users of the application. We are doing I in others platform providers by using configuring CRON jobs. This is a sort of missing feature in App Platform. looking forward to be available soon.
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.