Windows installation Gitlab

1. Basic Ideas

(1) Installing VMware in Windows Server 12 installs the Centos,centos internal installation Gitlab in VMware and accesses the Gitlab service directly from the host IP port through host port mapping.

2. Problem solving

(1) One of the top issues in this is the problem of networking, which resolves the virtual machine access network problem in NAT mode (which includes three network mode Host,bridge,nat by default), which will cause the Yum installation image to not be pulled.
Workaround:
1. Find information about the Linux network adapter ls/etc/sysconfig/network-scripts/
2. Editing system Issues vi/etc/sysconfig/network-scripts/ifcfg-eno16777736
The 3.ONBOOT option defaults to False, where Yes is checked, exit and save

3. Install Gitlab (login with Xshell, hide false machine)

Install dependent software
Yum-y install policycoreutils openssh-server openssh-clients postfix
2. Set postfix boot, and start, Postfix support Gitlab function
Systemctl enable Postfix && systemctl start postfix
3. Download the Gitlab installation package and install
Rpm-i git LAB-CE-8.0.0-CE.0.EL7.X86_64.RPM
4. Modify the Gitlab configuration file to specify the server IP and custom port:
vim/etc/gitlab/gitlab.rb
The URL Change to its own virtual machine IP port. The
exits and saves.
5. Compile the Gitlab package Gitlab-ctl reconfigure
6. Restart Gitlab gitlab-ctl Restart

3. To this Gitlab installation is complete, next there is a problem to resolve, virtual machine port limit issues, causing some ports after external access problems.

This issue is caused primarily by several reasons.

(1) The Linux firewall restricts external access, and the most brutal way to solve this problem is to shut down the Linux firewall directly.
Show firewall status Service iptable status Discovery Firewall is alive state.
Shut down the firewall by Servcie iptables stop, or permanently shut down the firewall through the STA.
(2) Linux rejected external HTTP link, this is my more tangled place, but also after the firewall is excluded, Xhell can be normal link and the HTTP request is rejected.
Workaround Settings Linux allows all types of packets to flow into
Iptables-f
Iptables-p INPUT ACCEPT
4. Set up extranet map access to map the virtual machine address and port to the host port.
(1) Edit the virtual machine NIC, set the routing mapping rules.
5. Set Linux boot up

6. Restart the machine will be unable to access the situation at this time only need to run a few two names to solve the problem
Iptables-f
Iptables-p INPUT ACCEPT

Windows installation Gitlab