gitlab

Gitlab6.0 and Apache2

孤者浪人 提交于 2020-01-01 18:58:35
问题 please how to set Github 6.0 with Apache2? Gitlab is installed according to the original instructions Adjustment in Unicorn.rb ... #listen "/home/git/gitlab/tmp/sockets/gitlab.socket", :backlog => 64 #listen "127.0.0.1:8080", :tcp_nopush => true listen "127.0.0.1:8080" ... My Apache2 conf is : <VirtualHost *:80> ServerName git.domain.com ErrorLog /var/log/apache2/gitlab_error.log CustomLog /var/log/apache2/gitlab_access.log combined ProxyRequests Off ProxyPreserveHost On ProxyPass / http:/

Gitlab 5.3 behind nginx reverse proxy

|▌冷眼眸甩不掉的悲伤 提交于 2020-01-01 18:54:11
问题 I have a successful Gitlab 5.3 install and everything works well. I want to run the server behind a nginx reverse proxy which I manage to do, but all the assets are missing: I have Gitlab running on /git and here is my nginx config on my reverse proxy server: server { listen 80 default; listen [::]:80 ipv6only=on default; server_name reverseproxy; ## redirect http to https rewrite ^ https://$server_name$request_uri? permanent; } server { access_log /var/log/nginx/ssl_access.log; error_log

Trouble installing gitlab-5.0. I can't finish the installation

天涯浪子 提交于 2020-01-01 18:27:41
问题 I am installing gitlab-5.0 on Ubuntu 10, when I execute the 'sudo gem install bundler' command on section Ruby of the gitlab installation guide, It shows me the next conflict: root@ubuntu:/home/gitlab/gitlab# sudo gem install bundler Successfully installed bundler-1.3.4 Installing ri documentation for bundler-1.3.4 /usr/lib/ruby/1.8/rdoc/rdoc.rb:280: warning: conflicting chdir during another chdir block /usr/lib/ruby/1.8/rdoc/rdoc.rb:287: warning: conflicting chdir during another chdir block

How does GitLab check for Grack HTTPS push permissions?

这一生的挚爱 提交于 2020-01-01 18:20:10
问题 I want develop some feature for GitLab and add it to open source repo. DESCRIPTION: When user make push, GitLab checks that all emails from commits should be present in database. I think to add some validation method to https://github.com/gitlabhq/gitlabhq/blob/master/lib/gitlab/git_access.rb this class, but this validation doesn't call when user push some changes (e.g. git push origin master). I've researched routing and found next: https://github.com/gitlabhq/gitlabhq/blob/master/config

How to use Dockerfile in Gitlab CI

老子叫甜甜 提交于 2020-01-01 17:13:06
问题 Using gitlab-ci for my node/react app, I'm trying to use phusion/passenger-nodejs as the base docker image I can specify this easily in .gitlab-ci.yml: image: phusion/passenger-nodejs:latest variables: HOME: /root cache: paths: - node_modules/ stages: - build - test - deploy set_environment: stage: build script: - npm install tags: - docker test_node: stage: test script: - npm install - npm test tags: - docker However, Phusion Passenger expects you to make configuration changes, e.g. python

bash: gitolite: command not found

旧街凉风 提交于 2020-01-01 16:46:10
问题 I am trying to make a new branch in Gitlab by using Gitolite. I complete the installation steps. when i come across "setting up gitolite" section i have a trouble. I followed this link. When i run gitolite setup -pk alice.pub command i got "bash: gitolite: command not found" error message. I don't know what is the problem.. Any one please help me. 回答1: This step comes after the Gitolite installation, which supposes you have chosen one of three possibilities: Keep the sources anywhere and use

“Could not open a connection to your authentication agent” ,ssh-add error even after ssh-agent started

|▌冷眼眸甩不掉的悲伤 提交于 2020-01-01 16:12:21
问题 I need to add multiple ssh keys , so i need to execute ssh-add But I get error of Could not open a connection to your authentication agent I read multiply posts like Could not open a connection to your authentication agent and https://superuser.com/questions/901568/ssh-agent-could-not-open-connection I had started the ssh-agent by eval ($ssh-agent -s) and the output is like : Agent pid 13524 but still get this error: $ ssh-add ~/.ssh/id_rsa Could not open a connection to your authentication

Git looking for my SSH key in the wrong location

半腔热情 提交于 2020-01-01 12:22:10
问题 I've been having a bit of a head ache with trying to pull down a repository held in Gitlab. This is all done in Windows 8.1 on a Ubuntu VM by the way if that helps. I've added my public key in Gitlab and added my private key to ssh-agent ... all seems correct. When I try and do a git pull this is where I run in to issues. It seems to me that Git is simply looking in the wrong location, my private key is stored in c/Users/Neil/.ssh but it seems as if git is looking in c/Users/Neil/.ssh/342/200

How do I find the real user who pushed a commit in gitlab?

ぐ巨炮叔叔 提交于 2020-01-01 10:17:22
问题 Is there a way to find out who pushed a particular commit to gitlab - In the commit log (I see the author set via the git client config) , I instead want to see which gitlab user's authentication was used to PUSH that code ? PS: There are multiple git specific questions asked and there was no solution provided in the previous questions - want to see if gitlab has some specific implementation to solve this ? 回答1: I answered "no" 5 years ago, but GitLab offers audit logs of its own: As

How do I find the real user who pushed a commit in gitlab?

懵懂的女人 提交于 2020-01-01 10:17:12
问题 Is there a way to find out who pushed a particular commit to gitlab - In the commit log (I see the author set via the git client config) , I instead want to see which gitlab user's authentication was used to PUSH that code ? PS: There are multiple git specific questions asked and there was no solution provided in the previous questions - want to see if gitlab has some specific implementation to solve this ? 回答1: I answered "no" 5 years ago, but GitLab offers audit logs of its own: As