Centos 安装gitlab

下载

下载页面下载centos版本对应的rpm包
https://www.gitlab.com/downloads/

###安装

sudo yum install openssh-server sudo yum install postfix # sendmail or exim is also OK sudo rpm -i gitlab-x.y.z_omnibus-x.el6.x86_64.rpm # this is the .rpm you downloaded sudo gitlab-ctl reconfigure sudo lokkit -s http -s ssh # open up the firewall for HTTP and SSH requests

就O了

安装后

执行 sudo gitlab-ctl status; 查看状态:

run: nginx: (pid 972) 7s; run: log: (pid 971) 7s run: postgresql: (pid 962) 7s; run: log: (pid 959) 7s run: redis: (pid 964) 7s; run: log: (pid 963) 7s run: sidekiq: (pid 967) 7s; run: log: (pid 966) 7s run: unicorn: (pid 961) 7s; run: log: (pid 960) 7s
nginx使用80端口, unicorn使用8080端口, 有冲突的话会启动失败
默认用户名 root 密码 5iveL!fe

官方安装文档

GitLab Omnibus project

This project creates full-stack platform-specific downloadable packages for GitLab. For other installation options please see the GitLab project README.

Documentation version

Please make sure you are viewing the documentation for the version of omnibus-gitlab you are using. In most cases this should be the highest numbered stable branch (example shown below).

documentation version

Installation

Please download the package and follow the steps below.

Ubuntu 12.04

sudo apt-get install openssh-server sudo apt-get install postfix # sendmail or exim is also OK sudo dpkg -i gitlab_x.y.z-omnibus-x.ubuntu.12.04_amd64.deb # this is the .deb you downloaded sudo gitlab-ctl reconfigure

Debian 7.4

sudo apt-get install openssh-server sudo apt-get install exim4-daemon-light sudo dpkg -i gitlab-x.y.z.deb # this is the .deb you downloaded sudo gitlab-ctl reconfigure

during the exim installation you may follow
http://alexatnet.com/references/server-setup-debian/send-only-mail-server-with-exim
to ensure you get a secure mailserver

CentOS 6.5

After installation

Run sudo gitlab-ctl status; the output should look like this:

Your GitLab instance should reachable over HTTP at the IP or hostname of
your server. You can login as an admin user with username root and
password 5iveL!fe.

Common installation problems

Reconfigure freezes at `ruby_block[supervise_redis_sleep] action run`

This happens when Runit has not been installed succesfully during
gitlab-ctl reconfigure. The most common cause for a failed Runit
installation is installing omnibus-gitlab on an unsupported platform.
Solution: double check on the download page whether you downloaded a
package for the correct operating system.

Updating

For update instructions, see the update guide.

Starting and stopping

After omnibus-gitlab is installed and configured, your server will have a Runit service directory (runsvdir) process running that gets started at boot via /etc/inittab or the /etc/init/gitlab-runsvdir.conf Upstart resource. You should not have to deal with the runsvdir process directly; you can use the gitlab-ctl front-end instead.

You can start, stop or restart GitLab and all of its components with the following commands.

shell

 Start all GitLab components

sudo gitlab-ctl start

Stop all GitLab components

sudo gitlab-ctl stop

 Restart all GitLab components

sudo gitlab-ctl restart

It is also possible to start, stop or restart individual components.

shell sudo gitlab-ctl restart unicorn

Configuration

Creating the gitlab.rb configuration file

shell sudo mkdir -p /etc/gitlab sudo touch /etc/gitlab/gitlab.rb sudo chmod 600 /etc/gitlab/gitlab.rb

Below several examples are given for settings in

/etc/gitlab/gitlab.rb. Please restart each time you made a change.

Configuring the external URL for GitLab

In order for GitLab to display correct repository clone links to your
users it needs to know the URL under which it is reached by your users,
e.g. http://gitlab.example.com. Add the following line to
/etc/gitlab/gitlab.rb:

ruby external_url "http://gitlab.example.com"

Run sudo gitlab-ctl reconfigure for the change to take effect.

Storing Git data in an alternative directory

By default, omnibus-gitlab stores Git repository data in
/var/opt/gitlab/git-data. You can change this location by adding the
following line to /etc/gitlab/gitlab.rb.

ruby git_data_dir "/mnt/nas/git-data"

Run sudo gitlab-ctl reconfigure for the change to take effect.

If you have an LDAP directory service such as Active Directory, you can
configure GitLab so that your users can sign in with their LDAP
credentials. Add the following to /etc/gitlab/gitlab.rb, edited for
your server.


These settings are documented in more detail at
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example\#L118

gitlab\_rails['ldap\_enabled'] = true gitlab\_rails['ldap\_host'] =
'hostname of LDAP server' gitlab\_rails['ldap\_port'] = 389
gitlab\_rails['ldap\_uid'] = 'sAMAccountName'
gitlab\_rails['ldap\_method'] = 'plain' \# 'ssl' or 'plain'
gitlab\_rails['ldap\_bind\_dn'] = 'CN=query
user,CN=Users,DC=mycorp,DC=com' gitlab\_rails['ldap\_password'] = 'query
user password' gitlab\_rails['ldap\_allow\_username\_or\_email\_login']
= true gitlab\_rails['ldap\_base'] = 'DC=mycorp,DC=com'

GitLab Enterprise Edition only

gitlab\_rails['ldap\_group\_base'] = '' \# Example:
'OU=groups,DC=mycorp,DC=com' gitlab\_rails['ldap\_user\_filter'] = '' \#
Example: '(memberOf=CN=my department,OU=groups,DC=mycorp,DC=com)'

Run sudo gitlab-ctl reconfigure for the LDAP settings to take effect.

Enable HTTPS

By default, omnibus-gitlab runs does not use HTTPS. If you want to enable HTTPS you can add the following line to /etc/gitlab/gitlab.rb.

ruby external_url "https://gitlab.example.com"

Redirect HTTP requests to HTTPS.

ruby external_url "https://gitlab.example.com" nginx['redirect_http_to_https'] = true

Change the default port and the ssl certificate locations.

ruby external_url "https://gitlab.example.com:2443" nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.crt" nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/gitlab.key"

Create the default ssl certifcate directory and add the files:

mkdir -p&& sudo chmod 700 /etc/gitlab/ssl

sudo cp gitlab.example.com.crt gitlab.example.com.key /etc/gitlab/ssl/

run lokkit to open https on the firewall

sudo lokkit -s https

if you are using a non standard https port

sudo lokkit -p 2443:tcp

Run sudo gitlab-ctl reconfigure for the change to take effect.

Changing gitlab.yml settings

Some of GitLab’s features can be customized through gitlab.yml. If you want to change a gitlab.yml setting with omnibus-gitlab, you need to do so via /etc/gitlab/gitlab.rb. The translation works as follows.

In gitlab.yml, you will find structure like this:

yaml production: &base gitlab: default_projects_limit: 10

In gitlab.rb, this translates to:

ruby gitlab_rails['gitlab_default_projects_limit'] = 10

What happens here is that we forget about production: &base, and join
gitlab: with default_projects_limit: into
gitlab_default_projects_limit. Note that not all gitlab.yml settings
can be changed via gitlab.rb yet; see the gitlab.yml ERB
template.
If you think an attribute is missing please create a merge request on
the omnibus-gitlab repository.

Run sudo gitlab-ctl reconfigure for changes in gitlab.rb to take
effect.

Backups

Creating an application backup

To create a backup of your repositories and GitLab metadata, run the
following command.

shell sudo gitlab-rake gitlab:backup:create

This will store a tar file in /var/opt/gitlab/backups. The filename
will look like 1393513186_gitlab_backup.tar, where 1393513186 is a
timestamp.

Scheduling a backup

To schedule a cron job that backs up your repositories and GitLab
metadata, use the root user:

sudo su - crontab -e

There, add the following line to schedule the backup for everyday at 2
AM:

0 2 * * * /opt/gitlab/bin/gitlab-rake gitlab:backup:create

Restoring an application backup

We will assume that you have installed GitLab from an omnibus package
and run sudo gitlab-ctl reconfigure at least once.

First make sure your backup tar file is in /var/opt/gitlab/backups.

shell sudo cp 1393513186_gitlab_backup.tar /var/opt/gitlab/backups/

Next, restore the backup by running the restore command. You need to
specify the timestamp of the backup you are restoring.


Stop processes that are connected to the database

sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq

DROP THE CURRENT DATABASE; workaround for a Postgres backup restore bug in GitLab 6.6

sudo -u gitlab-psql /opt/gitlab/embedded/bin/dropdb gitlabhq\_production

This command will overwrite the contents of your GitLab database!

sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186

Start GitLab

sudo gitlab-ctl start

If there is a GitLab version mismatch between your backup tar file and
the installed version of GitLab, the restore command will abort with an
error. Install a package for the required
version and try again.

Invoking Rake tasks

To invoke a GitLab Rake task, use gitlab-rake. For example:

shell sudo gitlab-rake gitlab:check

Contrary to with a traditional GitLab installation, there is no need to
change the user or the RAILS_ENV environment variable; this is taken
care of by the gitlab-rake wrapper script.

Directory structure

Omnibus-gitlab uses four different directories.

/opt/gitlab holds application code for GitLab and its
dependencies.
/var/opt/gitlab holds application data and configuration files
that gitlab-ctl reconfigure writes to.
/etc/gitlab holds configuration files for omnibus-gitlab. These
are the only files that you should ever have to edit manually.
/var/log/gitlab contains all log data generated by components of
omnibus-gitlab.

Starting a Rails console session

If you need access to a Rails production console for your GitLab
installation you can start one with the command below. Please be warned
that it is very easy to inadvertently modify, corrupt or destroy data
from the console.

shell sudo /opt/gitlab/bin/gitlab-rails console

This will only work after you have run gitlab-ctl reconfigure at least
once.

Using a non-packaged database management server

If you do not want to use the built-in Postgres server of omnibus-gitlab
or if you want to use MySQL (GitLab Enterprise Edition only) you can do
so as follows.

Important note: if you are connecting omnibus-gitlab to an existing
GitLab database you should create a backup before attempting this
procedure.

Create a user and database for GitLab

First, set up your database server according to the upstream GitLab
instructions.
If you want to keep using an existing GitLab database you can skip this
step.

Configure omnibus-gitlab to connect to it

Next, we add the following settings to /etc/gitlab/gitlab.rb.


Disable the built-in Postgres

postgresql['enable'] = false

Fill in the values for database.yml

gitlab\_rails['db\_adapter'] = 'mysql2' gitlab\_rails['db\_encoding'] =
'utf8' gitlab\_rails['db\_host'] = '127.0.0.1' gitlab\_rails['db\_port']
= '3306' gitlab\_rails['db\_username'] = 'git'
gitlab\_rails['db\_password'] = 'password'

Parameters such as db_adapter correspond to adapter in
database.yml; see the upstream GitLab examples for
Postgres and MySQL. We remind you that /etc/gitlab/gitlab.rb should have file permissions 0600 because it contains plaintext passwords.

Run sudo gitlab-ctl reconfigure for the change to take effect.

Seed the database (fresh installs only)

Omnibus-gitlab will not automatically seed your external database. Run
the following command to import the schema and create the first admin
user:

shell sudo gitlab-rake gitlab:setup

This is a destructive command; do not run it on an existing database!

Building your own package

See the separate build documentation.

Running a custom GitLab version

It is not recommended to make changes to any of the files in
/opt/gitlab after installing omnibus-gitlab: they will either conflict
with or be overwritten by future updates. If you want to run a custom
version of GitLab you can build your own package or use
another installation
method.

Acknowledgments

This omnibus installer project is based on the awesome work done by Chef
in
omnibus-chef-server.

Centos 安装gitlab

下载

安装后

Ubuntu 12.04

Debian 7.4

CentOS 6.5

After installation

Common installation problems

Reconfigure freezes at ruby_block[supervise_redis_sleep] action run

Creating the gitlab.rb configuration file

Below several examples are given for settings in

Configuring the external URL for GitLab

Storing Git data in an alternative directory

Setting up LDAP sign-in

Enable HTTPS

Changing gitlab.yml settings

Backups

Creating an application backup

Scheduling a backup

Restoring an application backup

Invoking Rake tasks

Directory structure

Starting a Rails console session

Using a non-packaged database management server

Create a user and database for GitLab

Configure omnibus-gitlab to connect to it

Seed the database (fresh installs only)

Building your own package

Running a custom GitLab version

Acknowledgments

Reconfigure freezes at `ruby_block[supervise_redis_sleep] action run`