![]() ![]() The best links I can find about this ( here, here, and here) do not seem to lead me to sufficient clarity to take an efficient guess as to what to do. But I have no idea if this should be a GitLab setting, an Nginx setting, a RoR setting, or some other setting and what the setting / setting file is. I do not see any settings in the GitLab web interface itself to change the host IP included with email invitations, so I assume I need to change a setting in a configuration file somewhere. However, I find that the URL provided in the invitation email is the local network IP address (i.e., 192.168.44.129) rather than the publicly visible static IP address. When inviting a user, an invitation/confirmation email is sent to that user that provides a link to login to the GitLab instance. ![]() Sending email needs to be enabled, requiring a modification of a settings file, and this worked straightforwardly ( here is a link that explains how to set up SMTP properly).īefore inviting new users, I wanted to test the functionality by inviting myself first (using a secondary email address). I have also successfully set up two Git repositories in the running GitLab instance. I am able to access the GitLab web interface from any internet-connected computer just by typing the static IP (including my chosen port). I have successfully gained public access to the GitLab application running as guest by setting up port forwarding within VMWare Workstation's Virtual Network Editor (using NAT translation, not bridging). My dedicated Windows server host has a publicly visible static IP address. I have set up a Bitnami GitLab stack as a running virtual machine instance using VMWare Workstation on my personal dedicated Windows server (host) running out of my home office. ![]()
0 Comments
Leave a Reply. |