maintenance.md 3.47 KB
Newer Older
1
### Gather information about GitLab and the system it runs on
2

3
4
This command gathers information about your GitLab installation and the System
it runs on. These may be useful when asking for help or reporting issues.
5
6

```
7
bundle exec rake gitlab:env:info RAILS_ENV=production
8
9
10
11
12
13
```

Example output:

```
System information
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
System:         Debian 6.0.6
Current User:   gitlab
Using RVM:      yes
RVM Version:    1.17.2
Ruby Version:   ruby-1.9.3-p327
Gem Version:    1.8.24
Bundler Version:1.2.3
Rake Version:   10.0.1

GitLab information
Version:        3.1.0
Resivion:       fd5141d
Directory:      /home/gitlab/gitlab
DB Adapter:     mysql2
URL:            http://localhost:3000
HTTP Clone URL: http://localhost:3000/some-project.git
SSH Clone URL:  git@localhost:some-project.git
Using LDAP:     no
Using Omniauth: no
33

34
35
GitLab Shell
Version:        1.0.4
36
Repositories:   /home/git/repositories/
37
Hooks:          /home/git/gitlab-shell/hooks/
38
Git:            /usr/bin/git
39
40
```

41

42
### Check GitLab configuration
43

44
45
46
Runs the following rake tasks:

* gitlab:env:check
47
48
* gitlab:gitlab_shell:check
* gitlab:sidekiq:check
49
50
51
52
53
* gitlab:app:check

It will check that each component was setup according to the installation guide and suggest fixes for issues found.

You may also have a look at our [Trouble Shooting Guide](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide).
54
55

```
56
bundle exec rake gitlab:check RAILS_ENV=production
57
58
59
60
61
```

Example output:

```
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Checking Environment ...

gitlab user is in git group? ... yes
Has no "-e" in ~git/.profile ... yes
Git configured for gitlab user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking Gitolite ...

Using recommended version ... yes
Config directory exists? ... yes
Config directory owned by git:git? ... yes
Config directory access is drwxr-x---? ... yes
Repo base directory exists? ... yes
Repo base owned by git:git? ... yes
80
Repo base access is drwxrws---? ... yes
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
post-receive hook exists? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ...
GitLab ... ok
Non-Ascii Files Test ... ok
Touch Commit Test ... ok
Without Master Test ... ok
Git config in repos: ...
GitLab ... ok
Non-Ascii Files Test ... ok
Touch Commit Test ... ok
Without Master Test ... ok

Checking Gitolite ... Finished

Checking Resque ...

Running? ... yes

Checking Resque ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is not SQLite ... yes
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config not outdated? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have satellites? ...
GitLab ... yes
Non-Ascii Files Test ... yes
Touch Commit Test ... yes
Without Master Test ... yes

Checking GitLab ... Finished
120
121
122
```


123
124
125
126
127
128
### (Re-)Create satellite repos

This will create satellite repos for all your projects.
If necessary, remove the `tmp/repo_satellites` directory and rerun the command below.

```
129
bundle exec rake gitlab:satellites:create RAILS_ENV=production
130
131
```

132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
### Import bare repositories into GitLab project instance

Notes:

* project owner will be a first admin
* existing projects will be skipped

How to use:

1. copy your bare repos under git base_path (see `config/gitlab.yml` git_host -> base_path)
2. run the command below

```
bundle exec rake gitlab:import:repos RAILS_ENV=production
```

Example output:

```
Processing abcd.git
 * Created abcd (abcd.git)
[...]
```