If you’re worrying about your filesystem, you should back up your system prior to making the configuration change.

That being said, I’m pretty sure that by default Nginx installs its files to a different location than stock packages (prefix /usr/local/)

@lexgabrees

When compiling from source, as in, downloading the source code from NGINX and running actual build commands from the CLI, you’re able to specify the exact location of where NGINX stores files as well as what directories NGINX will use for said storage. As long as you specify different locations, the previous versions’ files and directories should remain unmodified.

You could technically run ten versions of NGINX as long as you specify different locations and names. Each of which could even have it’s own init or systemd script (though you’d most likely need to modify the ones that come along with the compile or create your own).

When doing a non-standard build, you may also need to create the directories first, otherwise the build may error out since you’re telling NGINX to use directories that do not yet exist.