151 reputation
19
bio website hippycentral.org
location
age
visits member for 4 years, 11 months
seen Oct 11 at 14:11
Hippy is as Hippy does

Oct
13
awarded  Notable Question
Oct
11
comment How to use gitlab without hostname
Thanks, unfortunately I don't manage all of the (potential) client machines as we're also using external developers. At the moment they're not using git but the plan is to move our existing svn repos to git so I need a simple way to allow them to connect. Changing config only on the single machine that is causing this seemed the obvious answer, rather than making network wide changes or forcing external developers to change their setup.
Oct
11
asked How to use gitlab without hostname
Sep
24
awarded  Autobiographer
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
Agreed - it wants to sit on its own server. In the end my answer wasn't quite as simple. Editing the config file directly - despite dire warnings that the config ill be removed on updates - was the only solution. the install script couldn't cope with how I needed to set things up.
Aug
19
awarded  Scholar
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
Unfortunately as I installed the package from the URL in the question, I was discouraged from directly editing the config (and indeed at the next update I understand I'll need to tweak the settings again as they'll be overwritten by the ruby script that does the config) - but this answer sent me in the right direction so it gets +1.
Aug
19
accepted Using gitlab behind Apache proxy all generated urls are wrong
Aug
19
awarded  Commentator
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
thanks @gparent - making me look for gitlab.yml fixed the issue although at the top it tells me not to edit that file manually. making the changes directly in there did there trick though. Add an answer to that effect and I'll credit you for it.
Aug
19
revised Using gitlab behind Apache proxy all generated urls are wrong
added 16 characters in body
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
thanks all for comments so far - I've posted my apache config to make things a bit clearer about what's going on
Aug
19
revised Using gitlab behind Apache proxy all generated urls are wrong
deleted 52 characters in body
Aug
19
revised Using gitlab behind Apache proxy all generated urls are wrong
deleted 52 characters in body
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
@gparent - I don't know what you mean by "in the documentation" - I've tried variations of using localhost:8888 and the real domain name...at the moment nothing works and nginx insists on trying to use port 80
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
@mike - the question has now been updated to clarify - the server is a dev server with an existing apache setup. I wanted gitlab and it installed nginx so I'm having to proxy
Aug
19
comment Using gitlab behind Apache proxy all generated urls are wrong
@gparent - I am. I've repeated what I said in the question to clarify.
Aug
19
revised Using gitlab behind Apache proxy all generated urls are wrong
added 187 characters in body
Aug
19
comment Set gitlab external web port number
How did this help? I'm still not getting anywhere with this - gitlab is insisting on using port 80 - which it can't because apache is already using it. Any specifics about what you did? Changing ports in those files did nothing.
Aug
19
revised Using gitlab behind Apache proxy all generated urls are wrong
added nginx log output