Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Hi!
Updating nginx should not affect any config files that you have created or modified. You can update nginx to the latest version by running sudo apt-get update to update the package lists, followed by sudo apt-get install nginx.
If you want to be extra careful, you can back up the /etc/nginx directory which contains all of nginx’s config files.
sudo cp -r /etc/nginx /etc/nginx.pre-upgrade
After upgrading the package, you can delete /etc/nginx and move /etc/nginx.pre-upgrade back to /etc/nginx. However, as I said, it is unnecessary and completely optional to do it.
I just observed that a recent Nginx upgrade did the following:
The first bullet can be addressed… from my personalized site config I can serve my static files up from a different direction.
But I don’t know how to address the 2nd bullet. Upgrading Nginx essentially takes down your website and replaces it with a welcome page.