On 02/22/2015 10:45 PM, Paul Johnson wrote: > 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-ombibus should raise an error or warning when Apache > httpd is already running in port 80. Don't you think so? Its fatal otherwise > > What do gitlab users do when they have pre-existing projects that depend > on Apache. Is this where the re-configure gitlab to use Apache > instructions come into play? >
You can configure whatever external server you want. See [0] for more info. > I've been trying to figure out what's needed to have gitlab show up as > one of many services. Right now, it wants to answer at main server > address, not something like myserver.com/gitlab. > To configure GitLab in a relative url you should follow these steps [1], but I can't say these are implemented for the omnibus packages. > 2. Gitlab seems to be working, but I am baffled by these warnings/errors > at beginning of reconfigure output. > > > # sudo gitlab-ctl reconfigure > the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and > should not be loaded in the same Ruby VM > falling back to ffi which might work (or might not, no promises) This is just a warning, you can ignore it. It is already reported here with a temp fix [2]. > Starting Chef Client, version 11.12.2 > Compiling Cookbooks... > Recipe: gitlab::default > * directory[/etc/gitlab] action create > - change mode from '0755' to '0775' > - restore selinux security context > ...snip > > > Running handlers: > Running handlers complete > > Chef Client finished, 15/164 resources updated in 21.013299863 seconds > gitlab Reconfigured! > > # sudo gitlab-ctl status > run: logrotate: (pid 20041) 767s; run: log: (pid 488) 274372s > run: nginx: (pid 5931) 246160s; run: log: (pid 416) 274378s > run: postgresql: (pid 32684) 274416s; run: log: (pid 32683) 274416s > run: redis: (pid 32555) 274427s; run: log: (pid 32554) 274427s > run: sidekiq: (pid 21294) 129s; run: log: (pid 362) 274384s > run: unicorn: (pid 21373) 115s; run: log: (pid 313) 274390s > > That means it is running, yes? > Yup, that's natural output. > 3. When I try to follow along with the instructions for interacting with > gitlab, using functions like "gem" and "bundle", I get error messages > saying those programs are not found. Have you seen that too? > GitLab omnibus uses its own cli for these actions. What are you trying to achieve? There exist: gitlab-ctl gitlab-rails gitlab-rake gitlab-ci-rails gitlab-ci-rake [0] https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md#using-a-non-bundled-web-server [1] https://gitlab.com/gitlab-org/gitlab-ce/blob/9459e9db2470e9c50488811d1d0fcdd025a327d0/config/application.rb#L53 [2] https://gitlab.com/gitlab-org/omnibus-gitlab/issues/387 -- GPG : 0x3A7DDABC985EDC6E Blog: http://axilleas.me -- 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/54EB0970.7030807%40gmail.com. For more options, visit https://groups.google.com/d/optout.
