mirror of
https://github.com/NixOS/nixpkgs.git
synced 2024-11-16 23:03:40 +01:00
111 lines
3.2 KiB
XML
111 lines
3.2 KiB
XML
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
version="5.0"
|
|
xml:id="module-services-gitlab">
|
|
|
|
<title>Gitlab</title>
|
|
|
|
<para>Gitlab is a feature-rich git hosting service.</para>
|
|
|
|
<section><title>Prerequisites</title>
|
|
|
|
<para>The gitlab service exposes only an Unix socket at
|
|
<literal>/run/gitlab/gitlab-workhorse.socket</literal>. You need to configure a
|
|
webserver to proxy HTTP requests to the socket.</para>
|
|
|
|
<para>For instance, the following configuration could be used to use nginx as
|
|
frontend proxy:
|
|
|
|
<programlisting>
|
|
services.nginx = {
|
|
enable = true;
|
|
recommendedGzipSettings = true;
|
|
recommendedOptimisation = true;
|
|
recommendedProxySettings = true;
|
|
recommendedTlsSettings = true;
|
|
virtualHosts."git.example.com" = {
|
|
enableACME = true;
|
|
forceSSL = true;
|
|
locations."/".proxyPass = "http://unix:/run/gitlab/gitlab-workhorse.socket";
|
|
};
|
|
};
|
|
'';
|
|
</programlisting>
|
|
</para>
|
|
|
|
</section>
|
|
|
|
<section><title>Configuring</title>
|
|
|
|
<para>Gitlab depends on both PostgreSQL and Redis and will automatically enable
|
|
both services. In the case of PostgreSQL, a database and a role will be created.
|
|
</para>
|
|
|
|
<para>The default state dir is <literal>/var/gitlab/state</literal>. This is where
|
|
all data like the repositories and uploads will be stored.</para>
|
|
|
|
<para>A basic configuration with some custom settings could look like this:
|
|
|
|
<programlisting>
|
|
services.gitlab = {
|
|
enable = true;
|
|
databasePassword = "eXaMpl3";
|
|
initialRootPassword = "UseNixOS!";
|
|
https = true;
|
|
host = "git.example.com";
|
|
port = 443;
|
|
user = "git";
|
|
group = "git";
|
|
smtp = {
|
|
enable = true;
|
|
address = "localhost";
|
|
port = 25;
|
|
};
|
|
secrets.db_key_base = "ei3eeP1ohsh0uu3ad4YeeMeeheengah3AiZee2ohl4Ooj5mie4Ohl0vishoghaes";
|
|
extraConfig = {
|
|
gitlab = {
|
|
email_from = "gitlab-no-reply@example.com";
|
|
email_display_name = "Example GitLab";
|
|
email_reply_to = "gitlab-no-reply@example.com";
|
|
default_projects_features = { builds = false; };
|
|
};
|
|
};
|
|
};
|
|
</programlisting>
|
|
</para>
|
|
|
|
<para>If you're setting up a new Gitlab instance, generate a new
|
|
<literal>db_key_base</literal> secret to encrypt sensible data in the
|
|
database. If you're restoring an existing Gitlab instance, you must
|
|
specify the <literal>db_key_base</literal> secret from
|
|
<literal>config/secrets.yml</literal> in your Gitlab state folder.</para>
|
|
|
|
<para>Refer to <xref linkend="ch-options" /> for all available configuration
|
|
options for the <literal>services.gitlab</literal> module.</para>
|
|
|
|
</section>
|
|
|
|
<section><title>Maintenance</title>
|
|
|
|
<para>You can run Gitlab's rake tasks with <literal>gitlab-rake</literal>
|
|
which will be available on the system when gitlab is enabled. You will
|
|
have to run the command as the user that you configured to run gitlab
|
|
with.</para>
|
|
|
|
<para>For example, to backup a Gitlab instance:
|
|
|
|
<programlisting>
|
|
$ sudo -u git -H gitlab-rake gitlab:backup:create
|
|
</programlisting>
|
|
|
|
A list of all availabe rake tasks can be obtained by running:
|
|
|
|
<programlisting>
|
|
$ sudo -u git -H gitlab-rake -T
|
|
</programlisting>
|
|
</para>
|
|
|
|
</section>
|
|
|
|
</chapter>
|