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 least 2GB of RAM, otherwise gitlab-ctl reconfigure will give strange errors Ruby comes bundled inside the rpm/deb package, you need to call it by specifying the complete path into your gitlab installation. But for a "normal" installation I never needed those functions. -- 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/8bbc9b82-99b9-44a3-9c90-5e58bcd7bc10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
