App Platform

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.

I will be very nice to see the Bitbucket repos integration soon

There is no way to stop, restart or pause the app. For the maintenance needs, it's something that we need all the time.

I would like to see an option to modify Cloudflare behaviour or completely disable it for App Platform, since Cloudflare sometimes acts like a man-in-the-middle and modifies the sourcecode sent by the app, which means you can't really be sure that the client gets what you send from the app.

When you create a new app in app platform Cloudflare CDN is enabled by default. This creates a lot of overhead in requests if you use it with your own CDN. eg. My CDN -> App Platform Cloudflare CDN -> Origin server. We should be able to disable App platform’s CDN via App Platform settings.

The static site hosting is very limited atm. There is only a "custom page" option to define a single fallback page when a route is not found. That's by far not enough. If I host a static next.js app, I need to rewrite specific routes to an [id].html file, for example. There is no way to define headers. Basically all proper build tools have checksummed files that could be cached forever. Some Apps will require security headers to be set. There is no option to do that. I'd have a few suggestions on how that could be implemented: Extending the routing feature to add headers and placeholders. That could also benefit none static sites. But it would annoyingly require updating the app config when adding wildcard pages and requires effort when syncing beta and live apps. A different solution would be config files like netilfy's _redirects and _headers file. I'm not sure that i like the custom nature of those, but they could be versioned. The maximum premium solution would be to implement a subset of apache's .htaccess files, especially the RewriteRule, RewriteCondition and Header statements. Those could statically be parsed on deploy time. What I love most about that idea is that it can be locally tested and doesn't invent a new standard. But it's likely the most complicated way

With Docker Compose, you can provide a "depends_on" option that instructs Docker Compose to depend on another container. This will tell Docker Compose to only start once the container it depends on is up and healthy. This would be a great feature to add to the AppPlatform, especially for Docker containers. A use case would be a Web Server that depends on a Queue and it should only start once the Queue has started and reports healthiness.

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.

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.

We should be able to disable the starter domain in App Platform or create a 301 redirect to a custom domain. With this not being an option static sites are always duplicated, which is a terrible SEO practice. At the very least it would be nice being able to set a robots.txt file in the starter domain to prevent search engines from indexing it.