See [doc/settings/configuration.md](doc/settings/configuration.md#storing-git-data-in-an-alternative-directory).
If any of the processes is not behaving like expected, try tailing their logs
to see what is wrong.
##### Changing the name of the Git user / group
```
sudo gitlab-ctl tail postgresql
```
See [doc/settings/configuration.md](doc/settings/configuration.md#changing-the-name-of-the-git-user-group).
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`.
##### Setting up LDAP sign-in
### Common installation problems
See [doc/settings/ldap.md](doc/settings/ldap.md).
This section has been moved to the separate document [doc/common_installation_problems.md](doc/common_installation_problems.md).
##### Enable HTTPS
Section below remains for historical reasons(mainly to not break existing links). Each section contains the link to the new location.
See [doc/settings/nginx.md](doc/settings/nginx.md#enable-https).
##### Apt error 'The requested URL returned error: 403'
##### Redirect `HTTP` requests to `HTTPS`.
See [doc/common_installation_problems.md](doc/common_installation_problems.md#apt-error-the-requested-url-returned-error-403).
See [doc/settings/nginx.md](doc/settings/nginx.md#redirect-http-requests-to-https).
##### GitLab is unreachable in my browser
##### Change the default port and the ssl certificate locations.
See [doc/common_installation_problems.md](doc/common_installation_problems.md#gitlab-is-unreachable-in-my-browser).
See [doc/settings/nginx.md](doc/settings/nginx.md#change-the-default-port-and-the-ssl-certificate-locations).
##### GitLab CI shows GitLab login page
##### Use non-packaged web-server
See [doc/common_installation_problems.md](doc/common_installation_problems.md#gitlab-ci-shows-gitlab-login-page).
For using an existing Nginx, Passenger, or Apache webserver see [doc/settings/nginx.md](doc/settings/nginx.md#using-a-non-bundled-web-server).
##### Emails are not being delivered
##### Using a non-packaged PostgreSQL database management server
See [doc/common_installation_problems.md](doc/common_installation_problems.md#emails-are-not-being-delivered).
To connect to an external PostgreSQL or MySQL DBMS see [doc/settings/database.md](doc/settings/database.md)(MySQL support in the Omnibus Packages is Enterprise Only).
##### Reconfigure freezes at `ruby_block[supervise_redis_sleep] action run`
##### Using a non-packaged Redis instance
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-freezes-at-ruby_blocksupervise_redis_sleep-action-run).
See [doc/settings/redis.md](doc/settings/redis.md).
##### TCP ports for GitLab services are already taken
##### Adding ENV Vars to the Gitlab Runtime Environment
See [doc/common_installation_problems.md](doc/common_installation_problems.md#tcp-ports-for-gitlab-services-are-already-taken).
##### Git SSH access stops working on SELinux-enabled systems
##### Changing gitlab.yml settings
See [doc/common_installation_problems.md](doc/common_installation_problems.md#git-ssh-access-stops-working-on-selinux-enabled-systems
).
See [doc/settings/gitlab.yml.md](doc/settings/gitlab.yml.md).
##### Postgres error 'FATAL: could not create shared memory segment: Cannot allocate memory'
##### Specify numeric user and group identifiers
See [doc/common_installation_problems.md](doc/common_installation_problems.md#postgres-error-fatal-could-not-create-shared-memory-segment-cannot-allocate-memory).
See [doc/settings/configuration.md](doc/settings/configuration.md#specify-numeric-user-and-group-identifiers).
##### Reconfigure complains about the GLIBC version
##### Sending application email via SMTP
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-complains-about-the-glibc-version).
See [doc/settings/smtp.md](doc/settings/smtp.md).
##### Reconfigure fails to create the git user
##### Omniauth (Google, Twitter, GitHub login)
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-fails-to-create-the-git-user).
To remove all omnibus-gitlab data use `sudo gitlab-ctl cleanse`.
To remove all users and groups created by omnibus-gitlab, before removing the gitlab package (with dpkg or yum) run `sudo gitlab-ctl remove_users`. *Note* All gitlab processes need to be stopped before runnign the command.
If any of the processes is not behaving like expected, try tailing their logs
to see what is wrong.
## Updating
```
sudo gitlab-ctl tail postgresql
```
Instructions for updating your Omnibus installation and upgrading from a manual installation are in the [update doc](doc/update.md).
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`.
## Starting and stopping
#### 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
Note that you cannot use a Unicorn reload to update the Ruby runtime.
## Configuration
### Updating
### Backup and restore omnibus-gitlab configuration
All configuration for omnibus-gitlab is stored in `/etc/gitlab`. To backup your
configuration, just backup this directory.
Instructions for updating your Omnibus installation and upgrading from a manual installation are in the [update doc](doc/update.md).
```shell
# Example backup command for /etc/gitlab:
# Create a time-stamped .tar file in the current directory.
# The .tar file will be readable only to root.
sudo sh -c 'umask 0077; tar -cf $(date "+etc-gitlab-%s.tar") -C / etc/gitlab'
```
### Uninstalling omnibus-gitlab
You can extract the .tar file as follows.
To uninstall omnibus-gitlab, preserving your data (repositories, database, configuration), run the following commands.
```shell
# Rename the existing /etc/gitlab, if any
sudo mv /etc/gitlab /etc/gitlab.$(date +%s)
# Change the example timestamp below for your configuration backup
sudo tar -xf etc-gitlab-1399948539.tar -C /
```
# Stop gitlab and remove its supervision process
sudo gitlab-ctl uninstall
Remember to run `sudo gitlab-ctl reconfigure` after restoring a configuration
backup.
NOTE: Your machines SSH host keys are stored in a separate location at `/etc/ssh/`. Be sure to also [backup and restore those keys](https://superuser.com/questions/532040/copy-ssh-keys-from-one-server-to-another-server/532079#532079) to avoid man-in-the-middle attack warnings if you have to perform a full machine restore.
### 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 or edit the following line in
`/etc/gitlab/gitlab.rb`:
# Debian/Ubuntu
sudo dpkg -r gitlab
```ruby
external_url "http://gitlab.example.com"
# Redhat/Centos
sudo rpm -e gitlab
```
Run `sudo gitlab-ctl reconfigure` for the change to take effect.
To remove all omnibus-gitlab data use `sudo gitlab-ctl cleanse`.
To remove all users and groups created by omnibus-gitlab, before removing the gitlab package (with dpkg or yum) run `sudo gitlab-ctl remove_users`. *Note* All gitlab processes need to be stopped before runnign the command.
### Storing Git data in an alternative directory
### Common installation problems
By default, omnibus-gitlab stores Git repository data under
`/var/opt/gitlab/git-data`: repositories are stored in
`/var/opt/gitlab/git-data/repositories`, and satellites in
`/var/opt/gitlab/git-data/gitlab-satellites`. You can change the location of
the `git-data` parent directory by adding the following line to
`/etc/gitlab/gitlab.rb`.
This section has been moved to the separate document [doc/common_installation_problems.md](doc/common_installation_problems.md).
```ruby
git_data_dir "/mnt/nas/git-data"
```
Section below remains for historical reasons(mainly to not break existing links). Each section contains the link to the new location.
Note that the target directory and any of its subpaths must not be a symlink.
##### Apt error 'The requested URL returned error: 403'
Run `sudo gitlab-ctl reconfigure` forthe change to take effect.
See [doc/common_installation_problems.md](doc/common_installation_problems.md#apt-error-the-requested-url-returned-error-403).
If you already have existing Git repositories in `/var/opt/gitlab/git-data` you
can move them to the new location as follows:
##### GitLab is unreachable in my browser
```shell
# Prevent users from writing to the repositories while you move them.
sudo gitlab-ctl stop
See [doc/common_installation_problems.md](doc/common_installation_problems.md#gitlab-is-unreachable-in-my-browser).
# Only move 'repositories'; 'gitlab-satellites' will be recreated
# automatically. Note there is _no_ slash behind 'repositories', but there _is_ a
See [doc/common_installation_problems.md](doc/common_installation_problems.md#gitlab-ci-shows-gitlab-login-page).
# Double-check directory layout in /mnt/nas/git-data. Expected output:
# gitlab-satellites repositories
sudo ls /mnt/nas/git-data/
##### Emails are not being delivered
# Done! Start GitLab and verify that you can browse through the repositories in
# the web interface.
sudo gitlab-ctl start
```
See [doc/common_installation_problems.md](doc/common_installation_problems.md#emails-are-not-being-delivered).
### Changing the name of the Git user / group
##### Reconfigure freezes at `ruby_block[supervise_redis_sleep] action run`
By default, omnibus-gitlab uses the user name `git` for Git gitlab-shell login,
ownership of the Git data itself, and SSH URL generation on the web interface.
Similarly, `git` group is used for group ownership of the Git data. You can
change the user and group by adding the following lines to
`/etc/gitlab/gitlab.rb`.
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-freezes-at-ruby_blocksupervise_redis_sleep-action-run).
```ruby
user['username'] = "gitlab"
user['group'] = "gitlab"
```
##### TCP ports for GitLab services are already taken
Run `sudo gitlab-ctl reconfigure` for the change to take effect.
See [doc/common_installation_problems.md](doc/common_installation_problems.md#tcp-ports-for-gitlab-services-are-already-taken).
### Setting up LDAP sign-in
##### Git SSH access stops working on SELinux-enabled systems
See [doc/settings/ldap.md](doc/settings/ldap.md).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#git-ssh-access-stops-working-on-selinux-enabled-systems
).
### Enable HTTPS
##### Postgres error 'FATAL: could not create shared memory segment: Cannot allocate memory'
See [doc/settings/nginx.md](doc/settings/nginx.md#enable-https).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#postgres-error-fatal-could-not-create-shared-memory-segment-cannot-allocate-memory).
#### Redirect `HTTP` requests to `HTTPS`.
##### Reconfigure complains about the GLIBC version
See [doc/settings/nginx.md](doc/settings/nginx.md#redirect-http-requests-to-https).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-complains-about-the-glibc-version).
#### Change the default port and the ssl certificate locations.
##### Reconfigure fails to create the git user
See [doc/settings/nginx.md](doc/settings/nginx.md#change-the-default-port-and-the-ssl-certificate-locations).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#reconfigure-fails-to-create-the-git-user).
### Use non-packaged web-server
##### Failed to modify kernel parameters with sysctl
For using an existing Nginx, Passenger, or Apache webserver see [doc/settings/nginx.md](doc/settings/nginx.md#using-a-non-bundled-web-server).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#failed-to-modify-kernel-parameters-with-sysctl).
## Using a non-packaged PostgreSQL database management server
##### I am unable to install omnibus-gitlab without root access
To connect to an external PostgreSQL or MySQL DBMS see [doc/settings/database.md](doc/settings/database.md)(MySQL support in the Omnibus Packages is Enterprise Only).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#i-am-unable-to-install-omnibus-gitlab-without-root-access).
## Using a non-packaged Redis instance
##### gitlab-rake assets:precompile fails with 'Permission denied'
See [doc/settings/redis.md](doc/settings/redis.md).
See [doc/common_installation_problems.md](doc/common_installation_problems.md#gitlab-rake-assetsprecompile-fails-with-permission-denied).
### Adding ENV Vars to the Gitlab Runtime Environment
See [doc/settings/unicorn.md](doc/settings/unicorn.md).
### Setting the NGINX listen address or addresses
You can extract the .tar file as follows.
See [doc/settings/nginx.md](doc/settings/nginx.md).
```shell
# Rename the existing /etc/gitlab, if any
sudo mv /etc/gitlab /etc/gitlab.$(date +%s)
# Change the example timestamp below for your configuration backup
sudo tar -xf etc-gitlab-1399948539.tar -C /
```
### Inserting custom NGINX settings into the GitLab server block
Remember to run `sudo gitlab-ctl reconfigure` after restoring a configuration
backup.
See [doc/settings/nginx.md](doc/settings/nginx.md).
NOTE: Your machines SSH host keys are stored in a separate location at `/etc/ssh/`. Be sure to also [backup and restore those keys](https://superuser.com/questions/532040/copy-ssh-keys-from-one-server-to-another-server/532079#532079) to avoid man-in-the-middle attack warnings if you have to perform a full machine restore.
### Inserting custom settings into the NGINX config
See [doc/settings/nginx.md](doc/settings/nginx.md).
# Double-check directory layout in /mnt/nas/git-data. Expected output:
# gitlab-satellites repositories
sudo ls /mnt/nas/git-data/
# Done! Start GitLab and verify that you can browse through the repositories in
# the web interface.
sudo gitlab-ctl start
```
### Changing the name of the Git user / group
By default, omnibus-gitlab uses the user name `git` for Git gitlab-shell login,
ownership of the Git data itself, and SSH URL generation on the web interface.
Similarly, `git` group is used for group ownership of the Git data. You can
change the user and group by adding the following lines to
`/etc/gitlab/gitlab.rb`.
```ruby
user['username'] = "gitlab"
user['group'] = "gitlab"
```
Run `sudo gitlab-ctl reconfigure` for the change to take effect.
### Setting up LDAP sign-in
See [doc/settings/ldap.md](doc/settings/ldap.md).
### Enable HTTPS
See [doc/settings/nginx.md](doc/settings/nginx.md#enable-https).
#### Redirect `HTTP` requests to `HTTPS`.
See [doc/settings/nginx.md](doc/settings/nginx.md#redirect-http-requests-to-https).
#### Change the default port and the ssl certificate locations.
See [doc/settings/nginx.md](doc/settings/nginx.md#change-the-default-port-and-the-ssl-certificate-locations).
### Use non-packaged web-server
For using an existing Nginx, Passenger, or Apache webserver see [doc/settings/nginx.md](doc/settings/nginx.md#using-a-non-bundled-web-server).
## Using a non-packaged PostgreSQL database management server
To connect to an external PostgreSQL or MySQL DBMS see [doc/settings/database.md](doc/settings/database.md)(MySQL support in the Omnibus Packages is Enterprise Only).
## Using a non-packaged Redis instance
See [doc/settings/redis.md](doc/settings/redis.md).
### Adding ENV Vars to the Gitlab Runtime Environment
