1

Would be great to have a mention of engines/build pack docs ( https://docs.digitalocean.com/products/app-platform/reference/buildpacks/nodejs/ ) in the tutorial "Deploy a Next.js App to App Platform" ( https://docs.digitalocean.com/tutorials/app-nextjs-deploy/ ). Also, for the BuildPack docs, it would be usefull to have note of min/max version for engine fields. Had mine as 18, but build kept failing until revert to 17.

https://docs.digitalocean.com/products/app-platform/concepts/app-spec/ This page needs more info how to create the App Spec file. I found out later it is possible to use doctl apps spec validate , and doctl apps --spec file.yaml --upsert can be used to create/update the app, and doctl apps propose --spec file.yaml . Also the relation (or lack of) with the conventional paths of .do/app.yaml and .do/deploy.template.yaml should be explained. In my case the online UI didn't allow to detect my Dockerfile in specific location and had to use the app spec to define it. But I had very little clues on how to define the file.

In Windows, the best SSH tool is now Windows Terminal. You can also create the OpenSSH keypair in Windows. If you have a keypair and used it during Droplet setup, connect in Windows Terminal with ssh root@[YOUR_IP_ADDRESS] -p 22 -i ~/.ssh/[YOUR_PRIVATE_KEY_FILE]

It took me a long time to realise that I had to prefix the BINDABLE_NAME examples on this page with the service name for the resource specific variables to work. Maybe the documentation can show that better per bindable name example. ${my-service.BINDABLE_NAME} https://docs.digitalocean.com/products/app-platform/how-to/use-environment-variables/#resource-specific-variables So for database, ${HOSTNAME} should be ${my-db-service.HOSTNAME} in reality...

re: How to Connect to Droplets with the Droplet Console If we modify /etc/systemd/system/droplet-agent.service as you suggest to use a different sshd port number, what will happen to our changes when you update the package? IOW, how will our changes survive the package update?

This page https://docs.digitalocean.com/products/spaces/how-to/set-file-metadata/ says "Due to a known issue, file metadata headers like Content-Encoding are not passed through the CDN. Metadata headers are correctly set when fetching content directly from the origin." Can we get some explanation of what this known issue is and when it will be fixed? Ticket number or something? Amazon S3 doesn't have this problem

Document all available version of python. The current docs only show one version. As of posting 3.10.4 https://docs.digitalocean.com/products/app-platform/languages-frameworks/python/

is ipv6 static by default? when I created a droplet it made a ipv6 address by default - is it static? Documentation says if you're adding ipv6 on existing put in a static ipv6, but what about the one I already have?

Either remove the (Beta) tag from the CDN PoP locations list, or explain what (Beta) means in the context of the CDN PoP. Does it work or not?