GitLab has been designed to run from the main domain - thus it will
conflict with apache. There is nothing (simple) that I found that will
change that.
One thing you can do is putting GitLab on a different port and setup an
Apache redirect - look for gitlab.rb file.
GitLab should run on at leas
On 19.02.2015 01:00, Sytse Sijbrandij wrote:
I'm sorry to hear you won't be able to use GitLab because of this.
Just to clear that up:
That is (of course) not the reason. But it is a feature that some guys
have been missing (and I can see their point).
Thanks for your reply,
Johannes
In
Hi, I'm just testing gitlab and run into some problems that are not widely
discussed.
1. Apache web server is running on this system. I realized that Apache
httpd is blocking the omnibus nginx server. As soon as I turned off httpd,
I could get gitlab to open in browser.
Seems like gitlab-ombi
1) I do not know how to change the default installation path, but you can
the change the home path - look into the template and search for "home",
you will find answers to some of your other questions.
2) Each user can define a finite number of ssh keys for his profile, each
repository has acce
Thanks I will try it.
:Still I dont know
- if/how I can change the default gitlab installation path and the git
user name and home path.
- how can I use same ssh-key to few repositories.
- Is there anyway good tutorial.
Thanks.
בתאריך יום שישי, 20 בפברואר 2015 בשעה 07:49:
Is it possible to create groups inside groups ? I am using gitlab version
7.0.0
In gitolite managed environment I have repositories like this,
git@abc,com:sports/forge/baseball.git
using gitlab I am able to create only git@abc,com:sports/baseball.git
Is there a way I can achieve this ?
Th