So I played around with the server a little more and I was able to get it running but it's not in the optimal state I want it to be in.
I initially got the Gitlab 502 error to appear in the browser so I knew I was close. In the end it took shutting down two additional servers I have running on the same box, apache and tomcat, in order for the ports to be resolved. Ideally, due to financial constraints of my company, this server is going to serve as our dev environment, our git SCM server, as well as our CI server. here is the current state of the gitlab.rb: #external_url 'http://gitlab.example.com' > external_url 'http://255.255.255.255' > #redis['port'] = 1234 > #postgresql['port'] = 2345 > #unicorn['port'] = 3456 > unicorn['port'] = 8080 I'm not sure what unicorn is doing but it appears in my research that nginx:unicorn::httpd:tomcat. That may not be exact but the point is both are neccesary. I know it's a lot of overhead but ultimately on this one server I would like httpd to proxy to the nginx:unicorn side through port 80 so my urls look like the following: http://localhost/ http://localhost/app1 http://localhost/gitlab/users/sign-in http://localhost/jenkins Any insight to accomplish this would be helpful even if it's just from the gitlab side. I can figure out the virtual host stuff. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/b917e837-b096-4e1b-af6c-3329e351c29c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
