這裏輸入引用文本run as root!node
apt-get update -y apt-get upgrade -y apt-get install sudo -y
注意:在安裝一些文件須要手動編輯。若是您熟悉vim將其設置爲默認編輯器下面的命令。若是你不熟悉vim請跳過這並繼續使用默認編輯器。python
vim安裝並設置爲默認編輯器mysql
sudo apt-get install -y vim sudo update-alternatives --set editor /usr/bin/vim.basic
安裝所須要的包(須要編譯Ruby和原生擴展Ruby gems):nginx
sudo apt-get install -y build-essential zlib1g-dev libyaml-dev libssl-dev libgdbm-dev libreadline-dev libncurses5-dev libffi-dev curl openssh-server redis-server checkinstall libxml2-dev libxslt-dev libcurl4-openssl-dev libicu-dev logrotate python-docutils pkg-config cmake nodejs
若是你想使用Kerberos進行用戶身份驗證,而後安裝libkrb5-dev:git
sudo apt-get install libkrb5-dev
注意:若是你不知道什麼是Kerberos,你能夠假設你不須要它。 確保你有正確的版本,安裝Gitweb
Install Gitredis
sudo apt-get install -y git-core
Make sure Git is version 1.7.10 or higher, for example 1.7.12 or 2.0.0sql
git --version
系統打包Git太老了嗎?刪除它從源代碼和編譯。shell
Remove packaged Git數據庫
sudo apt-get remove git-core
Install dependencies
sudo apt-get install -y libcurl4-openssl-dev libexpat1-dev gettext libz-dev libssl-dev build-essential
Download and compile from source
cd /tmp curl -L --progress https://www.kernel.org/pub/software/scm/git/git-2.4.6.tar.gz | tar xz cd git-2.4.6/ ./configure make prefix=/usr/local all
Install into /usr/local/bin
sudo make prefix=/usr/local install
When editing config/gitlab.yml (Step 5), change the git -> bin_path to /usr/local/bin/git 注意:爲了接收郵件通知,必定要安裝一個郵件服務器。默認狀況下,Debian附帶exim4但這問題,而不附帶一個Ubuntu。推薦的郵件服務器是後綴,您能夠安裝:
sudo apt-get install -y postfix
Then select 'Internet Site' and press enter to confirm the hostname 2. Ruby
使用Ruby版本經理如RVM rbenv或chruby GitLab生產常常致使難以診斷的問題。例如,GitLab殼被稱爲從OpenSSH和版本管理器能夠防止拖在SSH。版本不支持經理和咱們強烈建議你們遵循下 面的說明使用Ruby的系統。 刪除舊的Ruby 1.8若是存在
sudo apt-get remove ruby1.8
Download Ruby and compile it:
mkdir /tmp/ruby && cd /tmp/ruby curl -L --progress http://cache.ruby-lang.org/pub/ruby/2.2/ruby-2.2.2.tar.gz | tar xz curl -L --progress https://ruby.taobao.org/mirrors/ruby/ruby-2.2.2.tar.gz | tar xz cd ruby-2.2.2 ./configure --disable-install-rdoc make sudo make install
Install the Bundler Gem: ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://api.rubygems.org/quick/Marshal.4.8/bundler-1.10.5.gemspec.rz) sudo gem install bundler --no-ri --no-rdoc ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://api.rubygems.org/quick/Marshal.4.8/bundler-1.10.5.gemspec.rz)
報錯處理 是由於國內網絡致使rubygems.org存放在Amazon S3上面的資源文件間歇性鏈接失敗,用國內的RubyGems鏡像(參見http://ruby.taobao.org/)替換官方鏡像,方法以下:
[root@h77 ruby-2.0.0-p353]# gem sources --remove https://rubygems.org/ https://rubygems.org/ removed from sources [root@h77 ruby-2.0.0-p353]# gem sources -a https://ruby.taobao.org/ https://ruby.taobao.org/ added to sources [root@h77 ruby-2.0.0-p353]# gem sources -l *** CURRENT SOURCES *** https://ruby.taobao.org/ gem install rails
若是你使用 Gemfile 和 Bundle (例如:Rails 項目) 你能夠用bundle的gem源代碼鏡像命令。
$ bundle config mirror.https://rubygems.org https://ruby.taobao.org
sudo adduser --disabled-login --gecos 'GitLab' git
Install the database packages
sudo apt-get install -y postgresql postgresql-client libpq-dev
Login to PostgreSQL
sudo -u postgres psql -d template1
Create a user for GitLab Do not type the 'template1=#', this is part of the prompt
template1=# CREATE USER git CREATEDB;
Create the GitLab production database & grant all privileges on database
template1=# CREATE DATABASE gitlabhq_production OWNER git;
Quit the database session
template1=# \q
Try connecting to the new database with the new user
sudo -u git -H psql -d gitlabhq_production
Quit the database session
gitlabhq_production> \q
sudo apt-get install redis-server
Configure redis to use sockets
sudo cp /etc/redis/redis.conf /etc/redis/redis.conf.orig
Disable Redis listening on TCP by setting 'port' to 0
sed 's/^port .*/port 0/' /etc/redis/redis.conf.orig | sudo tee /etc/redis/redis.conf
Enable Redis socket for default Debian / Ubuntu path
echo 'unixsocket /var/run/redis/redis.sock' | sudo tee -a /etc/redis/redis.conf
Grant permission to the socket to all members of the redis group
echo 'unixsocketperm 770' | sudo tee -a /etc/redis/redis.conf
Create the directory which contains the socket
mkdir /var/run/redis chown redis:redis /var/run/redis chmod 755 /var/run/redis
Persist the directory which contains the socket, if applicable
if [ -d /etc/tmpfiles.d ]; then echo 'd /var/run/redis 0755 redis redis 10d -' | sudo tee -a /etc/tmpfiles.d/redis.conf fi
Activate the changes to redis.conf
sudo service redis-server restart
Add git to the redis group
sudo usermod -aG redis git
We'll install GitLab into home directory of the user "git"
cd /home/git
Clone the Source
Clone GitLab repository
sudo -u git -H git clone https://gitlab.com/gitlab-org/gitlab-ce.git -b 7-12-stable gitlab
Note: You can change 7-12-stable to master if you want the bleeding edge version, but never install master on a production server!
Configure It
Go to GitLab installation folder
cd /home/git/gitlab
Copy the example GitLab config
sudo -u git -H cp config/gitlab.yml.example config/gitlab.yml
Update GitLab config file, follow the directions at top of file
sudo -u git -H editor config/gitlab.yml
Make sure GitLab can write to the log/ and tmp/ directories
sudo chown -R git log/ sudo chown -R git tmp/ sudo chmod -R u+rwX,go-w log/ sudo chmod -R u+rwX tmp/
Create directory for satellites
sudo -u git -H mkdir /home/git/gitlab-satellites sudo chmod u+rwx,g=rx,o-rwx /home/git/gitlab-satellites
Make sure GitLab can write to the tmp/pids/ and tmp/sockets/ directories
sudo chmod -R u+rwX tmp/pids/ sudo chmod -R u+rwX tmp/sockets/
Make sure GitLab can write to the public/uploads/ directory
sudo chmod -R u+rwX public/uploads
Copy the example Unicorn config
sudo -u git -H cp config/unicorn.rb.example config/unicorn.rb
Find number of cores
nproc
Enable cluster mode if you expect to have a high load instance Ex. change amount of workers to 3 for 2GB RAM server Set the number of workers to at least the number of cores
sudo -u git -H editor config/unicorn.rb
Copy the example Rack attack config
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
Configure Git global settings for git user, used when editing via web editor
sudo -u git -H git config --global core.autocrlf input
Configure Redis connection settings
sudo -u git -H cp config/resque.yml.example config/resque.yml
Change the Redis socket path if you are not using the default Debian / Ubuntu configuration
sudo -u git -H editor config/resque.yml
Important Note: Make sure to edit both gitlab.yml and unicorn.rb to match your setup. Note: If you want to use HTTPS, see Using HTTPS for the additional steps. Configure GitLab DB Settings
sudo -u git cp config/database.yml.postgresql config/database.yml
MySQL only:
sudo -u git cp config/database.yml.mysql config/database.yml
MySQL and remote PostgreSQL only: Update username/password in config/database.yml. You only need to adapt the production settings (first part). If you followed the database guide then please do as follows: Change 'secure password' with the value you have given to $password You can keep the double quotes around the password
sudo -u git -H editor config/database.yml
PostgreSQL and MySQL: Make config/database.yml readable to git only
sudo -u git -H chmod o-rwx config/database.yml
Install Gems Note: As of bundler 1.5.2, you can invoke bundle install -jN (where N the number of your processor cores) and enjoy the parallel gems installation with measurable difference in completion time (~60% faster). Check the number of your cores with nproc. For more information check this post. First make sure you have bundler >= 1.5.2 (run bundle -v) as it addresses some issues that were fixed in 1.5.2.
For PostgreSQL (note, the option says "without ... mysql")
sudo -u git -H bundle install --deployment --without development test mysql aws kerberos
Or if you use MySQL (note, the option says "without ... postgres")
sudo -u git -H bundle install --deployment --without development test postgres aws kerberos
國內: 在gitlab目錄修改文件 vi Gemfile 文件的https://rubygems.org/ 爲 https://ruby.taobao.com/
Note: If you want to use Kerberos for user authentication, then omit kerberos in the --without option above. Install GitLab Shell GitLab Shell is an SSH access and repository management software developed specially for GitLab. Run the installation task for gitlab-shell (replace `REDIS_URL` if needed): sudo -u git -H bundle exec rake gitlab:shell:install[v2.6.3] REDIS_URL=unix:/var/run/redis/redis.sock RAILS_ENV=production
By default, the gitlab-shell config is generated from your main GitLab config. You can review (and modify) the gitlab-shell config as follows:
sudo -u git -H editor /home/git/gitlab-shell/config.yml Note: If you want to use HTTPS, see Using HTTPS for the additional steps. Note: Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1 hostname"). This might be necessary for example if you set up gitlab behind a reverse proxy. If the hostname cannot be resolved, the final installation check will fail with "Check GitLab API access: FAILED. code: 401" and pushing commits will be rejected with "[remote rejected] master -> master (hook declined)". Initialize Database and Activate Advanced Features sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production
Type 'yes' to create the database tables.
When done you see 'Administrator account created:' Adding limits to schema.rb for mysql == Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb Administrator account created: ``` login.........root password......5iveL!fe Note: You can set the Administrator/root password by supplying it in environmental variable GITLAB_ROOT_PASSWORD as seen below. If you don't set the password (and it is set to the default one) please wait with exposing GitLab to the public internet until the installation is done and you've logged into the server the first time. During the first login you'll be forced to change the default password.
這一步能夠不作,有可能引發登陸不了gitlab
sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production GITLAB_ROOT_PASSWORD=yourpassword
Install Init Script Download the init script (will be /etc/init.d/gitlab):
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
And if you are installing with a non-default folder or user copy and edit the defaults file: sudo cp lib/support/init.d/gitlab.default.example /etc/default/gitlab If you installed GitLab in another directory or as a user other than the default you should change these settings in /etc/default/gitlab. Do not edit /etc/init.d/gitlab as it will be changed on upgrade. Make GitLab start on boot:
sudo update-rc.d gitlab defaults 21
Setup Logrotate
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
Check Application Status Check if GitLab and its environment are configured correctly:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
Compile Assets
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
Start Your GitLab Instance
sudo service gitlab start
> or
sudo /etc/init.d/gitlab restart
7. Nginx Note: Nginx is the officially supported web server for GitLab. If you cannot or do not want to use Nginx as your web server, have a look at the GitLab recipes. Installation
sudo apt-get install -y nginx
Site Configuration Copy the example site config:
sudo cp lib/support/nginx/gitlab /etc/nginx/sites-available/gitlab sudo ln -s /etc/nginx/sites-available/gitlab /etc/nginx/sites-enabled/gitlab
Make sure to edit the config file to match your setup: > Change YOUR_SERVER_FQDN to the fully-qualified > domain name of your host serving GitLab. > If using Ubuntu default nginx install: > either remove the default_server from the listen line > or else rm -f /etc/sites-enabled/default
sudo editor /etc/nginx/sites-available/gitlab Note: If you want to use HTTPS, replace the gitlab Nginx config with gitlab-ssl. See Using HTTPS for HTTPS configuration details.
Test Configuration Validate your gitlab or gitlab-ssl Nginx config file with the following command:
sudo nginx -t
錯誤:nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/gitlab:43 nginx: configuration file /etc/nginx/nginx.conf test failed sudo rm -f /etc/nginx/sites-enabled/default # 這是一個ln文件,推薦 sudo service nginx restart You should receive syntax is okay and test is successful messages. If you receive errors check your gitlab or gitlab-ssl Nginx config file for typos, etc. as indicated in the error message given. Restart
sudo service nginx restart
Done! Double-check Application Status To make sure you didn't miss anything run a more thorough check with: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production If all items are green, then congratulations on successfully installing GitLab! NOTE: Supply SANITIZE=true environment variable to gitlab:check to omit project names from the output of the check command. Initial Login Visit YOUR_SERVER in your web browser for your first GitLab login. The setup has created a default admin account for you. You can use it to log in: 郵件配置 1. 配置好服務器的主機名
root@git:/home/git# vim /etc/hostname
git 2. 安裝 postfix
root@git:apt-get install postfix -y
Then select 'Internet Site' and press enter to confirm the hostname. gitlab郵件提醒配置,建立帳號,添加SSH KEY的時候都會有郵件提醒給用戶。 修改全局配置文件git/.gitconfig文件,這裏的email是gitlab發送郵件的Email地址。
root@git:/home/git# pwd /home/git root@git:/home/git# ll total 36 drwxr-xr-x 4 git git 4096 Apr 10 16:11 ./ drwxr-xr-x 5 root root 4096 Feb 21 13:42 ../ -rw-r--r-- 1 git git 220 Mar 29 2013 .bash_logout -rw-r--r-- 1 git git 3527 Dec 23 11:28 .bashrc drwx------ 2 git git 4096 Dec 23 13:52 .cache/ -rw-rw-r-- 1 git git 50 Apr 10 16:11 .gitconfig -rw-r--r-- 1 root root 48 Mar 31 17:45 .gitconfig.bak lrwxrwxrwx 1 root root 44 Dec 23 11:28 gitlab-shell -> /opt/gitlab-6.3.0-1/apps/gitlab/gitlab-shell/ -rw-r--r-- 1 git git 716 Dec 23 11:28 .profile drwx------ 2 git git 4096 Feb 21 13:44 .ssh/ root@git:/home/git# vim .gitconfig [user] name = GitLab email = gitlab@lixiaoyi.com
當管理員給用戶建立帳號時,用戶郵箱裏面會自動收到gitlab發送的郵件。