GitSwarm 2016.3-2 Documentation

Maintenance

Maintenance

Gather information about GitSwarm and the system it runs on

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

# package installations
sudo gitswarm-rake gitswarm:env:info

# source installation
bundle exec rake gitswarm:env:info RAILS_ENV=production

Example output:

System information
System:           Debian 7.8
Current User:     git
Using RVM:        no
Ruby Version:     2.1.5p273
Gem Version:      2.4.3
Bundler Version:  1.7.6
Rake Version:     10.3.2
Sidekiq Version:  2.17.8

GitSwarm information
Version:          7.7.1
Revision:         41ab9e1
Directory:        /home/git/gitlab
DB Adapter:       postgresql
URL:              https://gitswarm.example.com
HTTP Clone URL:   https://gitswarm.example.com/some-project.git
SSH Clone URL:    [email protected]:some-project.git
Using LDAP:       no
Using Omniauth:   no

GitLab Shell
Version:          2.4.1
Repositories:     /home/git/repositories/
Hooks:            /home/git/gitlab-shell/hooks/
Git:              /usr/bin/git

Check GitSwarm configuration

Runs the following rake tasks:

gitswarm:gitlab_shell:check
gitswarm:sidekiq:check
gitswarm: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 GitSwarm's Trouble Shooting Guide.

# package installations
sudo gitswarm-rake gitswarm:check

# source installation
bundle exec rake gitswarm:check RAILS_ENV=production

NOTE: Use SANITIZE=true for gitswarm:check if you want to omit project names from the output.

Example output:

Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version? ... OK (1.2.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... yes

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitSwarm ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitSwarm config exists? ... yes
GitSwarm config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Redis version >= 2.0.0? ... yes

Checking GitSwarm ... Finished

Rebuild authorized_keys file

In some case it is necessary to rebuild the authorized_keys file.

For GitSwarm packages:

sudo gitswarm-rake gitswarm:shell:setup

For source installations:

cd /home/git/gitlab
sudo -u git -H bundle exec rake gitswarm:shell:setup RAILS_ENV=production

This will rebuild an authorized_keys file.
You will lose any data stored in authorized_keys file.
Do you want to continue (yes/no)? yes

Clear redis cache

If for some reason the dashboard shows wrong information you might want to clear Redis' cache.

For GitSwarm packages:

sudo gitswarm-rake cache:clear

For source installations:

cd /home/git/gitlab
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production

Precompile the assets

Sometimes during version upgrades you might end up with some wrong CSS or missing some icons. In that case, try to precompile the assets again.

Note that this only applies to source installations and does NOT apply to package installations.

For source installations:

cd /home/git/gitlab
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production

For package installations, the unoptimized assets (JavaScript, CSS) are frozen at the release of upstream GitSwarm. The package installation includes optimized versions of those assets. Unless you are modifying the JavaScript / CSS code on your production machine after installing the package, there should be no reason to redo rake assets:precompile on the production machine. If you suspect that assets have been corrupted, you should reinstall the package installation.

Tracking Deployments

GitSwarm provides a Rake task that lets you track deployments in GitSwarm Performance Monitoring. This Rake task simply stores the current GitSwarm version in the GitSwarm Performance Monitoring database.

For GitSwarm packages:

sudo gitswarm-rake gitswarm:track_deployment

For source installations:

cd /home/git/gitlab
sudo -u git -H bundle exec rake gitswarm:track_deployment RAILS_ENV=production