Gitlab git http server fixes

• git_data_dir support
• enable gitlab-git-http-server by default
• bump gitlab-git-http-server to 0.2.9 (profiler support)

mentioned in issue #753 (closed)

mentioned in issue #749 (closed)

Milestone changed to 8.0

Reassigned to @marin

Milestone changed to 8.0

If gitlab-git-http-server is enabled by default, why do we need a config therefore?

@razer6 all services in omnibus-gitlab can be disabled. I think it is sane to keep this consistent.

On gitlab.com we use omnibus packages to run postgres and redis on the 'backend' server. We would not want to enable gitlab-git-http-server on that machine.

Thanks for clarification.

Status changed to merged

mentioned in commit e6fa1b77

Thanks for asking @razer6

mentioned in issue #749 (closed)

@jacobvosmaer I just updated to master on my local development environment and noticed my HTTP requests were quietly failing with odd errors. Then I realized this change had occurred. Does gitlab-git-http-server need to be run as part of a foreman task?

@stanhu yes we need to come up with something

@stanhu see https://gitlab.com/gitlab-org/gitlab-development-kit/compare/faba4099...30e62def6487ab03c30d8f6bf94566fe47ee4b62