Documentation

Add domain to App via curl is incomplete: https://docs.digitalocean.com/products/app-platform/how-to/manage-domains/

My Gitlab repo uses large file support for some of the larger site media resources, and I'd like to know how I can pull them into a static site during deployment via git.

The documentation at https://docs.digitalocean.com/products/spaces/how-to/enable-versioning/ is incomplete. There's nothing that says how to restore a previous version of a Spaces object.

I was going through the following tutorial: https://docs.digitalocean.com/products/kubernetes/getting-started/deploy-image-to-cluster/ But I ran into all sort of issues when actually deploying the app to Digital Ocean. Half an hour of troubleshooting later, it turns out this was because I built my container on my M1 MacBook Pro (ARM64) and my docker container was AMD64. While I feel like I learned something because I perservered (with ChatGPT's assistance), it wasn't the easy start I was hoping for!

Not sure what is expected for schema migrations. I will use drizzle or kyzley to model my db and generate migration scripts. Is the best practice to run those via a containerized db-admin server, or another way? I seem to have mysql workbench connected to my db, so I could run it locally in theory. I am hoping as I set all this up, I'll be able to trigger a db migration off the mono repo push when a migration is present.

On this doc: https://docs.digitalocean.com/products/networking/reserved-ips/how-to/find-anchor-ips/ Make it clearer that the IP in the curl commands is actually a genuine DigitalOcean owned IP and that the user needs to hit the curl command as in the example, whilst SSH'd into the droplet. I was getting confused thinking that my droplet had a metadata API exposed so was changing the IP for my droplet's own IP and curling it externally. Also, have an example of the full set anchor metadata; if the user uses an IP other-than the anchor gateway IP in the next command, they'll get disconnected and have to power cycle the droplet. This could be avoided with some improved docs. Thanks!

with console access feature, it requires the SSH source IP within DigitalOcean IP ranges, the source IP is not customer client IP. if somehow customer want to restrict the Cloud Firewalls inbound rules only with known source IP, console access may timeout. it will be helpful if you update such info in product doc. client computer web -- SSH agent in US -- Droplets you want to login

redis-cli does support TLS with the --tls flag, so that part of the documentation which states that it does not is incorrect.

The docs have this note for the Node Buildpack: Note Long Term Support (LTS) versions of Node.js are not supported. This is not true. Node 22.1, which is in Active LTS, is supported in the engine field of package.json. The docs also say they only support upto 21.x, which is also not true.

In the "doctl compute firewall create ..." docs, it's not clear how to specify a tag in the new rule. Does one specify "address:<tag>", even tho it's not a network address. Secondly, I'd like to create a rule where the tag contains a ':' (e.g. the "k8s:worker" tag). Is the tool going to confuse the ':' in the tag name with another field specifier in the rule? An example would suffice. Thanks