Documentation

When kubernetes versions are updated we need more detail than "internal updates to the base image." That doesn't tell us anything. Was a CVE patched? What was the update. Review Google, Azure, and AWS documentation for examples.

Actually, I haven't found where I can report again a very bad tutorial, that I reported a year ago and no actions were done. Unfortunately, I opened this manual again, but didn't recognize it, and now I spent a day to figure out that this freaking loop (the last one) doesn't work in my code. so, maybe someone could review my comment (that I posted last year) and attach/post it to this manual, or just block the manual https://www.digitalocean.com/community/tutorials/if-else-in-shell-scripts

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

https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mariadb-php-lamp-stack-on-debian-11 there is a big error in the apache config. i post here the whole code <VirtualHost *:80> ServerName farms.xvf ServerAlias www.farms7.1 ServerAdmin webmaster@localhost DocumentRoot /home/user/farms ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined </VirtualHost> This does not work, gives a 403 error. <VirtualHost *:80> <Directory /home/user/farms> Options Indexes FollowSymLinks AllowOverride All Require all granted </Directory> DocumentRoot /home/user/farms </VirtualHost> This works. no use changing all the permissions and all. tried and tested. hence update. and send reply via email.

It is not completely intuitive or obvious for everyone what each cache status means, so the documentation should include that to make it clearer for the user.

The Docs pages for How to Forward Logs are great, but they are missing a paragraph that explains what is actually logged by default. Typically for many DB's the logs would be default message levels of WARNING and above, as is the case for PostgreSQL. It would be nice if the Docs pages detailed what the log content level defaults are for each DB and what those levels each typically contain. If Managed DB's use default logging configurations from each DB vendor, then that should be explained in the Docs pages.

It is unclear from the documentation whether it is possible to obtain the private network configuration of the database via Component-Specific variables.

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.

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!

I started by searching for a way to visualise logs that are stored in my logs folders. I then found an article by Digital Ocean's Erin Glass which helped a great deal in getting things up and running. Although I had several concerns over stability and also thought what if I could have everything, ie: all tooling under one roof. I then ported the install to Kali Linux, to try to see whether it'd be possible. Instead of using Nginx, I used Apache2 web server. As a final product, the entire solution was installed on Kali Linux. If you would like a write-up, you may contact me at abrnet@outlook.com .