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.
Hello friend!
I should let you know that this is not going to feel like a trivial task by any means, and what you are looking to do will not be the easiest path to resolution. Much easier would be to run other websites on another server. GitLab is plenty resource intensive to justify not sharing a server with other tasks. With that said, if you want to continue, I can only give you a direction and not a step by step process. I cannot guarantee that updates will not conflict and cause any changes here to fail later.
The config file for the Nginx that is bundled with GitLab on our one-click image, which is serving the GitLab instance over http, is /var/opt/gitlab/nginx/conf/nginx.conf. Changes here may be removed later by gitlab-ctl.
If you run a different instance of the web server to do this task, you can at least reference that nginx.conf file to find the configurations (note the includes as well) that you would want to carry over to your new configurations, so that it would continue to load GitLab as desired.
Kind Regards, Jarland