XiphInfra:GitLab VM: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
After making changes to the <code>gitlab.rb</code>, you need to run <code>sudo gitlab-ctl reconfigure</code> for the changes to be applied to the actual config files. '''Under no circumstances edit the generated config files directly''', always use the <code>gitlab.rb</code> config. | After making changes to the <code>gitlab.rb</code>, you need to run <code>sudo gitlab-ctl reconfigure</code> for the changes to be applied to the actual config files. '''Under no circumstances edit the generated config files directly''', always use the <code>gitlab.rb</code> config. | ||
In case you made an error in the configuration and something is not working as expected or some components, for example nginx, are not starting anymore, you can use <code>sudo gitlab-ctl tail</code> to view logs. | |||
Latest revision as of 04:16, 28 May 2021
IP blocks
We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance.
The IP blocks are configured in /etc/gitlab/gitlab.rb in the nginx['custom_gitlab_server_config'] option. Additionally there is a custom error page for when the IP is blocked, which is stored at /var/www/html/gitlab-ipblock.html.
After making changes to the gitlab.rb, you need to run sudo gitlab-ctl reconfigure for the changes to be applied to the actual config files. Under no circumstances edit the generated config files directly, always use the gitlab.rb config.
In case you made an error in the configuration and something is not working as expected or some components, for example nginx, are not starting anymore, you can use sudo gitlab-ctl tail to view logs.