Yeah have tried that.

Does not work for me.  I have gitlab running on port 4000.  

        ProxyPass /gitlab http://127.0.0.1:4000/
        ProxyPassReverse /gitlab http://127.0.0.1:4000/

I can access gitlab directly through my address.

It does something then gives me a 404 error.


On Thursday, December 4, 2014 2:04:38 PM UTC, Jeroen de Neef wrote:
>
> You can keep the unicorn port on the default settings, I kept mine on the 
> default settings as well.
> Find *gitlab.rb*, mine is in */etc/gitlab*
> You should have something like *external_url "http://example.com:80/ 
> <http://example.com:80/>"* and you should change the port number, if 
> there isn't a port number or no external_url you should add it.
> Save it and *sudo gitlab-ctl reconfigure*
>
> If you use VirtualHost on Apache you can have something like 
> git.example.com instead of example.com/git
>
> If you want to use SSL/TLS and port 443 is already in use you can do 
> something like this in gitlab.rb
> *external_url "https://example.com:2443/ <https://example.com:2443/>"*
> *nginx['ssl_certificate'] = "/dir/to/cert/example.com.pem"*
> *nginx['ssl_certificate_key'] = "/dir/to/cert/example.com.key"*
>
> 2014-12-04 13:09 GMT+01:00 Robbie McTavish <riy...@gmail.com <javascript:>
> >:
>
>> Ah I'll try that.
>>
>> How do i configure the nginx port and should i configure the unicorn port 
>> also?
>>
>> On Wednesday, December 3, 2014 9:57:16 AM UTC, Jeroen de Neef wrote:
>>>
>>> Oops, I left something incorrect in it because I copied it from my 
>>> config and forgot to edit some parts.
>>>
>>> *ProxyRequests Off*
>>> *ProxyPass / http://127.0.0.1:8000/ <https://127.0.0.1:8000/>*
>>> *ProxyPassReverse / http://127.0.0.1:8000/ <https://127.0.0.1:8000/>*
>>> *ProxyPreserveHost On*
>>> *<Location />*
>>> *AddOutputFilterByType SUBSTITUTE text/html*
>>> *Substitute "s|http://example.com:8000|http://example.com:80|i"*
>>> *</Location>*
>>> *<Proxy *>*
>>> *     Order deny,allow*
>>> *     Allow from all*
>>> *</Proxy>*
>>>
>>> This should be correct.
>>>
>>> 2014-12-03 10:55 GMT+01:00 Jeroen de Neef <jero...@gmail.com>:
>>>
>>>> An easy solution to that issue that I also use myself is by running it 
>>>> on nginx on lets say port 8000 and configure in Apache to reverse proxy it.
>>>>
>>>> This is what I think that you should have in your config, I have about 
>>>> the same and even went the extra mile and installed a certificate.
>>>>
>>>> *ProxyRequests Off*
>>>> *ProxyPass / https://127.0.0.1:8000/ <https://127.0.0.1:8000/>*
>>>> *ProxyPassReverse / https://127.0.0.1:8000/ <https://127.0.0.1:8000/>*
>>>> *ProxyPreserveHost On*
>>>> *<Location />*
>>>> *AddOutputFilterByType SUBSTITUTE text/html*
>>>> *Substitute "s|http://example.com:8000|http://example.com:80|i"*
>>>> *</Location>*
>>>> *<Proxy *>*
>>>> *     Order deny,allow*
>>>> *     Allow from all*
>>>> *</Proxy>*
>>>>
>>>> I hope that this will help you on the way.
>>>>
>>>> 2014-12-03 9:35 GMT+01:00 Robbie McTavish <riy...@gmail.com>:
>>>>
>>>>> I use apache to host all the other services via port 80.  So I would 
>>>>> rather have it also run through apache to prevent it having to be 
>>>>> addressed 
>>>>> on a separate port.
>>>>>
>>>>> On Tuesday, December 2, 2014 8:03:29 PM UTC, Jeroen de Neef wrote:
>>>>>>
>>>>>> If I may ask, what is preventing you from running GitLab on nginx?
>>>>>>
>>>>>> 2014-12-02 16:48 GMT+01:00 Robbie McTavish <riy...@gmail.com>:
>>>>>>
>>>>>>> 4 Core x64 CPU
>>>>>>> 32 Gig RAM
>>>>>>> 800 Gigs of Storage
>>>>>>>
>>>>>>> VM running on a Vsphere server
>>>>>>>
>>>>>>> If I run it with nginx it loads quickly but apache just churns
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, December 2, 2014 3:24:47 PM UTC, Jeroen de Neef wrote:
>>>>>>>>
>>>>>>>> Hi Robbie,
>>>>>>>>
>>>>>>>> Could you list the specs from the server such as the cpu and the 
>>>>>>>> RAM?
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>> Jeroen
>>>>>>>> Op 2 dec. 2014 16:20 schreef "Robbie McTavish" <riy...@gmail.com>:
>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> After much mucking about I finally got gitlab to run with Apache. 
>>>>>>>>>   i have used the apache configs from the repo and altered ports.
>>>>>>>>>
>>>>>>>>> However when pointed at the address for gitlab the pages take 
>>>>>>>>> upwards of 5 minutes to load.
>>>>>>>>>
>>>>>>>>> I can see nothing in the apache logs.
>>>>>>>>>
>>>>>>>>> Does anyone have any idea why it may be taking so long to load 
>>>>>>>>> pages?
>>>>>>>>>
>>>>>>>>> nginx is disabled.
>>>>>>>>> unicorn is on port 4000
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards 
>>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>>>> Groups "GitLab" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>>> send an email to gitlabhq+u...@googlegroups.com.
>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>> https://groups.google.com/d/msgid/gitlabhq/a09d6e94-4db7-459
>>>>>>>>> e-a1de-cac71a43f508%40googlegroups.com 
>>>>>>>>> <https://groups.google.com/d/msgid/gitlabhq/a09d6e94-4db7-459e-a1de-cac71a43f508%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>> .
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>  -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "GitLab" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>> send an email to gitlabhq+u...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/gitlabhq/7d0ca710-a823-4c0
>>>>>>> 4-88a6-79c5e0440b6d%40googlegroups.com 
>>>>>>> <https://groups.google.com/d/msgid/gitlabhq/7d0ca710-a823-4c04-88a6-79c5e0440b6d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>  -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "GitLab" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to gitlabhq+u...@googlegroups.com.
>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>> msgid/gitlabhq/3d49a4b9-307a-47c8-a817-54c238cd9d79%40googlegroups.com 
>>>>> <https://groups.google.com/d/msgid/gitlabhq/3d49a4b9-307a-47c8-a817-54c238cd9d79%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GitLab" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to gitlabhq+u...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/gitlabhq/43890cf0-a6ea-4454-b7be-9a63a175b255%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/gitlabhq/43890cf0-a6ea-4454-b7be-9a63a175b255%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/27692efe-eeba-4fb2-9eb5-dde68d2e5c68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to