App Platform

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

It should be possible to access a deployed App Platform app via ssh, in addition to the web Console. At times, the web Console is flaky, disconnecting arbitrarily. This has led to issues when running scripts, such as a database migration command, where the script is interrupted. Offering conventional SSH access would be a more reliable solution.

Currently, when deploying an app using app platform, the only way to access the app's console is via the web control panel and clicking on the console tab under the app in app platform.Ideally, there would be a feature to be able to get directly into this console from a command line using doctl and the app id, similar to what is possible with heroku.

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

The current browser-based console is very limited. It would be really nice if you could do something analogous to docker exec in the doctl CLI. For example: doctl apps exec <app id> <component name> <command> [args] .

I could not find a way to tell if I can enable http3 in app platform. Its all the hype right now and we saw what http2 did for us. Can http3 be used in app platform? Is it enabled already? Can someone tell me what the deal is because i cannot find any information on the net.

DO App Patform doesn't seem to support a way to define folders that can be persisted across builds. A use case: Next.js has a .next/.cache folder that's recommended to be persisted across builds. In Heroku, you can define this in config as such: "cacheDirectories": [".next/cache"] https://nextjs.org/docs/messages/no-cache

It should be possible to deploy apps directly from GitHub container registry. As many ppl use workflows for CI & CD.

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.