I just installed Gitlab on Ubuntu using the guide @ https://about.gitlab.com/install/#ubuntu
So far I’m facing 3 serious issues which are preventing me from progressing further:
- No application appears to be installed. I can’t find an icon in the Ubuntu Dash, nor can I see a way of launching it via terminal, or search.
- It appears to have accidentally installed Ruby on Rails. How do I remove it?
- It wanted me to install OpenSSH, which (for security reasons) this is a non-starter. We use https for secure connections, and although I was told the “/etc/gitlab/gitlab.rb” file could be configured for this purpose, opening the file reveals an empty document.
Your help would be greatly appreciated.
Thank you, rev. It may seem simple thing, but I feel like your feedback is invaluable knowledge I wish had been posted somewhere on the homepage. I really was expecting a desktop application.
I physically use Ubuntu, and manage it from the desktop UI as I would with any of my other computers. I get that applications will want to initiate an encrypted connection over its port and protocol, but that’s not all it does; SSH is a security risk as it presents a remote admin control vector that could otherwise be avoided.
As such, we try to mitigate the number of ports that are actually open and pointed at the server. I was expecting to open one port for Git, itself. For a collaboration tool, one additional port is also workable, however… from the documentation I’ve been able to find (https://docs.gitlab.com/omnibus/package-information/defaults.html), GitLab has a nightmare list of ports for it to be fully configured.
GitLab seems like a cool product, but (in its current form) it seems like I’m not a target market for it. I don’t know that you would, but if you could, it’d be great to see a desktop application that opened only a couple ports to do its business.
GitLab uses the ports to communicate with all services.
If you install GitLab on a desktop to be used by yourself only, you can keep you machine completely locked down using a firewall etc.
If other users need access to the GitLab instance, you’ll need to open up http/s access for them.