Currently the doc explains heroku-buildpack-nodejs is used by App Platform, so it supports the same versions. But heroku-buildpack-nodejs supports Node.js 18.x whereas App Platform doesn't. Please document all available version of Node.js runtime.

How to Deploy Functions to App Platform article really don't have an answer. There is no real information how to structure project in the config file if require deploy function to app platform

Here's what I did instead: nmcli connection modify "cloud-init eth0" ipv6.method manual nmcli connection modify "cloud-init eth0" ipv6.address 2604:a880:400:d0::xxxx:yyyy/64 nmcli connection modify "cloud-init eth0" ipv6.gateway 2604:a880:400:d0::1 nmcli connection modify "cloud-init eth0" ipv6.dns "2001:4860:4860::8844 2001:4860:4860::8888" nmcli connection up "cloud-init eth0"

All DO Documentation mentions Posted and Validated Date, however the are usually old. Now since these documentations are updated often. Last Updated date will help visitors understand it is regularly maintained and updated and does not only have old data/information

https://docs.digitalocean.com/products/databases/postgresql/how-to/modify-user-privileges/ Currently the article does not mention that databases are publicly accessible by default and how to change this. To restrict each database to one user the following commands can be used: BEGIN; -- by default, everybody can connect REVOKE CONNECT ON DATABASE "dbname" FROM PUBLIC; -- now you have to grant access to the legitimate users specifically GRANT CONNECT ON DATABASE "dbname" TO "username"; COMMIT; Also should mention the default public accessibility in https://docs.digitalocean.com/products/databases/postgresql/how-to/manage-users-and-databases/

Trying to figure out how to run a custom build command. Can't find the option anywhere and the docs are broken.

https://docs.digitalocean.com/tutorials/app-nextjs-deploy/ It doesn't seem like it's necessary to use define a custom "export" command in package.json or to use a _static/ directory. It seems like the App Platform is smart enough to work with the default Next.js behaviors. Also, it's unclear if the static vs. dynamic configurations in the tutorial are actually working. It seems like the app is running with dynamic rendering either way. The screenshots do not match what I'm seeing in my dashboard in 2023. The last issue I encountered is that the app refuses to start because of missing image-optimization configuration. I had to add the following to my next.config.js file: images: { unoptimized: true }

It would be useful to know exactly which files are rewritten during this process so that it is possible to convert those files to a new format when needed (eg. after upgrading the distribution or installing a distribution not available by default, ..) For a Fedora 17-based image, it seems to rewrite : /etc/passwd (whether or not a SSH key has been specified - which is a bit annoying as there's then no way to know the root password when a key has been specified) /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-eth0 Any other? Is the distribution auto-detected by the configuration-rewriting script (so that it rewrites what it thinks works for that distro) or somehow the initial distribution used to create the snapshot is stored by DO as well?

The documentation says that the maximum timeout for functions is 15 minutes, but it's not possible to change the 3 seconds timeout (which is very small)

Need some documentation describing the differences between namespaces and app platform in the view of "Functions" service (implying the service not the literal word). I just started with serverless and It has become really confusing to develop DO's functions. I think the confusion arised because the CLI creates a namespace to deploy functions, whereas there should be a way to deploy to app platform without pushing every small thing to GitHub. While this was okay but now when I'm in need of adding a BUILD ONLY env var, I can do it easily on the App Platform, but I can't seem to do it on Namespaces. It just strengthens my confusion between Namespace and App platform