Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Omnibus GitLab on IP without a domain-name and with custom relative_url_root

Tags:

gitlab

I already know that you can download and install gitlab with the omnibus package(easy way). But I'm caught at the configuration of the IP / domain. Because I don't have a domain I want to use my static server IP like this:

Sudo gitlab-ctl reconfigure -> "133.713.37.01/gitlab"

Is it even possible to set up gitlab without a domain or am I doing something wrong?

I'm grateful for any help

like image 851
ComputerDully Avatar asked Oct 28 '14 19:10

ComputerDully


People also ask

What is GitLab omnibus package?

Omnibus GitLab is a downloadable package that contains all the components needed to run, configure, and scale a self-managed instance of GitLab on prem or in the cloud. It provides a quick and easy way to install a standard instance of GitLab and keep it updated to the latest version.

Can you host your own GitLab?

Gitlab Is Like Your Own Hosted Github Unlike Github though, Gitlab's community edition is open source, and free for you to host on your own private server.

What is GitLab server URL?

The instance URL of any GitLab install is basically the link to the GitLab you're trying to connect to. For example, if your project is hosted on gitlab.example.com/yourname/yourproject then for the instance URL enter https://gitlab.example.com .


1 Answers

Using IP directly seems work, since most networking utilities accept either: just add external_url "http://127.0.0.1" to /etc/gitlab/gitlab.rb and run sudo gitlab-ctl reconfigure.

What does not work is adding the /gitlab root path to the external_url: gitlab-ctl says:

RuntimeError
------------
Unsupported external URL path: /gitlab

Serving from a relative URL root seems to be simply not implemented on Omnibus GitLab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/ed51ec97401bba955c93e61f8ef860520f745837/files/gitlab-cookbooks/gitlab/templates/default/gitlab.yml.erb#L24 (since no template variable is inserted there)

You could work around that by modifying all the required configuration files manually as explained in the comment on gitlab.yml, but that would really be a lot of manual work and those configs would get overwritten if you reconfigure, so I recommend you request the feature at: http://feedback.gitlab.com/forums/176466-general and send a pull request implementing that.