In short, it allows you to keep track of changes made to the source code of a software (commit) and its versions (tags), work in parallel on another “branch” of the same software (branch) and merge your\u00a0changes with those of other developers (merge).<\/p>\n
Everything is managed by a repository, the most famous of which is GitHub<\/a>,\u00a0which is nevertheless an online repository.<\/p>\n This tutorial is aimed at all those who wish\u00a0to have a personal\u00a0(and possibly private) Git repository on their own\u00a0server, in the particular case in which it has a\u00a0CentOS operating system with Parallels Plesk and use GitLab<\/a> as repository platform.<\/p>\n In this case, the coexistence of GitLab, Nginx and Plesk virtual hosts can become difficult to manage: if you are\u00a0reading this, maybe it’s because on the Internet\u00a0there is just\u00a0fragmented information on how to proceed without problems, hence the reason for this tutorial.<\/p>\n So we begin: assume you have a Linux CentOS v6.5 server with Plesk installed (we used version 12.5.30 as a reference, but the procedure has also been tested on version 12.0.18).<\/p>\n Assuming of course that you are root on the server or that your\u00a0user at least belongs to the list of sudoers<\/em>, in order to have rights to install packages. The first thing to do is to install the latest version of Git<\/strong> (currently 1.8.3.1) from PUIAS Computational repository:<\/p>\n or, for the latest version (currently 2.6.1):<\/p>\n Verify its installation with:<\/p>\n What we need is to install Ruby<\/strong>, as GitLab was designed for\u00a0Ruby v2.0+, although it might work with older\u00a0versions such as the one available in the CentOS repository. For quick installation of the older version (currently 1.8.7.374) you can use the following command:<\/p>\n If you want the latest\u00a0version (2.1.2 at the time), you can just run the following commands to install the prerequisites, the\u00a0OpenSSL extension and Ruby:<\/p>\n Now use the gem command to install Bundler<\/strong>, a dependencies manager for Ruby:<\/p>\n <\/p>\n At this point, having completed the prerequisites, you must add the server for\u00a0the GitLab CE (Community Edition) package with:<\/p>\n and finally install the package (about 328 Mb download, 904 Mb installation for version 8.0.4) with:<\/p>\n Now we got GitLab installed on our server, in the \/var\/opt\/gitlab\/ folder<\/strong>, which however must be configured according to our needs.<\/p>\n Suppose you want your Git repository to be available for example at the\u00a0address http:\/\/git.nullalo.com. The first thing to do is edit the \/etc\/gitlab\/gitlab.rb file<\/strong> and change the following values (above each of them we put a note with\u00a0the\u00a0meaning):<\/p>\n To use GitLab with SSL protocol<\/strong> you need to change external_url and add an option as follows:<\/p>\n If you need to use an HTTPS port other than the default (443), just specify it as part of the external_url:<\/p>\n If your GitLab version is 8.0.x<\/strong> or 8.1.x<\/strong>, you must also change the settings for the new gitlab-git-http-server<\/a><\/strong>, since Apache cannot connect to a UNIX socket but instead needs to connect to a TCP Port:<\/p>\n Starting from version 8.2, gitlab-git-http-server has been replaced by new version\u00a0gitlab-workhorse<\/a><\/strong>, a daemon that handles downloads too. Therefore, for GitLab 8.2.x<\/strong> you must ignore above gitlab_git_http_server settings and insert:<\/p>\n If you want GitLab to\u00a0send you emails, edit in the same file also SMTP server\u00a0settings<\/strong> by typing in the\u00a0server’s host (in the example mail.nullalo.com), port (usually 25, if you do not use SSL\/TLS) username and password to be used and authentication type (“plain” in our example):<\/p>\n To move data folder in your virtual host’s one<\/strong>:<\/p>\n To move uploads folder<\/strong> as well:<\/p>\n If you wish to set backup folder and schedule<\/strong>:<\/p>\n Now reconfigure and start GitLab<\/strong> with previous settings using the command:<\/p>\n Pay particular attention when moving\u00a0GitLab folders<\/strong> in the\u00a0virtual host’s ones: if right permissions are not set, those folders won’t\u00a0be backupped by Plesk. For it is essential\u00a0that GitLab works with git user and group, and it enforces 700 as permissions on\u00a0both data (\/var\/opt\/gitlab\/git-date\/) and\u00a0backup (\/var\/opt\/gitlab\/backups) folders, the quickest solution is to change folders permissions<\/strong> after each reconfiguration of GitLab (gitlab-ctl reconfigure), so that Plesk can back them\u00a0up. This can be done with the following command:<\/p>\n <\/p>\n Now that GitLab is configured and running, the most delicate part is on our way: Plesk integration<\/strong>.<\/p>\n Create \/etc\/nginx\/conf.d\/gitlab.conf<\/strong>\u00a0file with the following content for GitLab version 7:<\/p>\n or the following for version 8.0.x\/8.1.x, which introduces gitlab-git-http-server:<\/p>\n or finally this for version 8.2.x, which introduces gitlab-workhorse:<\/p>\n To avoid 413 error\u00a0when committing large amount of data<\/strong>,\u00a0just\u00a0verify that the http section\u00a0of\u00a0\/etc\/sw-cp-server\/config file contains the following line:<\/p>\n Then edit \/etc\/nginx\/nginx.conf file and add the same line in the http section:<\/p>\n Reload\u00a0nginx with:<\/p>\n or restart the service with:<\/p>\n Now, in Plesk, create a new domain or subdomain, for example\u00a0git.nullalo.com, and in its configuration click on \u201cApache & nginx Settings\u201d (“Web server settings” on\u00a0Plesk 12.0) for the chosen domain. Uncheck all the options in the “nginx settings” section and add the following text in the “Additional nginx directives” textarea for GitLab 7:<\/p>\n or the following one for GitLab 8.0.x\/8.1.x (with gitlab-git-http-server):<\/p>\n or the following for GitLab 8.2.x (with gitlab-workhorse):<\/p>\n <\/p>\n Navigate to the URL of the chosen domain (example http:\/\/git.nullalo.com) and login with the default GitLab credentials:<\/p>\n Change password on first login.<\/p>\n Once you login with the new credentials, you will finally have access to GitLab.<\/p>\n At this point, if you want to access the repository via\u00a0SSH instead of HTTP, you need to generate a public SSH-2 RSA key<\/strong> for your client.<\/p>\n On Windows you can use Git Bash (already included with Git for Windows<\/a>) or PuTTy<\/a>‘s\u00a0puttygen.exe command. On Linux or in the first case, once launched Git Bash from the Start menu, the command is:<\/p>\n On Linux, the generated public key can be read with:<\/p>\n while on Windows it will be located in the following path:<\/p>\n At this point you have to set SSH key for your profile<\/strong>. Click on “Profile Settings” or the profile (root) icon on the bottom left of the GitLab page to access the profile settings:<\/p>\n then click on\u00a0\u201cSSH Keys\u201d in the left menu and finally on the \u201cAdd SSH Key\u201d button on the top right corner of the window.<\/p>\n Type in a name for your key (basically your email or client’s name) in the \u201cTitle\u201d field, paste the public key in the \u201cKey\u201d field and click on \u201cAdd key\u201d.<\/p>\nPhase\u00a01 – Prerequisites<\/h2>\n
wget -O \/etc\/yum.repos.d\/PUIAS_6_computational.repo https:\/\/gitlab.com\/gitlab-org\/gitlab-recipes\/raw\/master\/install\/centos\/PUIAS_6_computational.repo\r\nwget -O \/etc\/pki\/rpm-gpg\/RPM-GPG-KEY-puias http:\/\/springdale.math.ias.edu\/data\/puias\/6\/x86_64\/os\/RPM-GPG-KEY-puias\r\nrpm --import \/etc\/pki\/rpm-gpg\/RPM-GPG-KEY-puias\r\nsudo yum install git<\/pre>\n
yum install gettext-devel expat-devel curl-devel zlib-devel openssl-devel\r\ncd \/tmp\r\nwget https:\/\/www.kernel.org\/pub\/software\/scm\/git\/git-2.6.1.tar.gz\r\ntar xzvf git-2.6.1.tar.gz\r\ncd git-2.6.1\r\nmake prefix=\/opt\/git all\r\nmake prefix=\/opt\/git install\r\nexport PATH="\/opt\/git\/bin:$PATH"\r\nln -s \/opt\/git\/bin\/git \/usr\/bin\/git<\/pre>\n
git --version<\/pre>\n
yum install ruby<\/pre>\n
yum install gcc zlib zlib-devel openssl-devel\r\nmkdir \/tmp\/ruby && cd \/tmp\/ruby\r\ncurl --progress ftp:\/\/ftp.ruby-lang.org\/pub\/ruby\/2.1\/ruby-2.1.2.tar.gz | tar xz\r\ncd ruby-2.1.2\/ext\/openssl\/\r\nruby extconf.rb\r\nmake top_srcdir="..\/..\/"\r\nsudo make install top_srcdir="..\/..\/"\r\ncd ..\/..\/\r\n.\/configure --disable-install-rdoc\r\nmake\r\nsudo make prefix=\/usr\/local install<\/pre>\n
gem install bundler --no-doc<\/pre>\n
Phase\u00a02 \u2013 GitLab<\/h2>\n
curl https:\/\/packages.gitlab.com\/install\/repositories\/gitlab\/gitlab-ce\/script.rpm.sh | sudo bash<\/pre>\n
sudo yum install gitlab-ce<\/pre>\n
# External URL for the GitLab repository\r\nexternal_url 'http:\/\/git.nullalo.com'\r\n# Completely disable GitLab's Nginx, since we're going to use the Plesk one\r\nnginx['enable'] = false\r\n# Sets server SSH port\r\ngitlab_rails['gitlab_shell_ssh_port'] = 22<\/pre>\n
external_url 'https:\/\/git.nullalo.com'\r\nnginx['listen_https'] = false # to communicate with GitLab Nginx internally over HTTP, even if external_url is in HTTPS\r\nnginx['redirect_http_to_https'] = true # redirects all traffic to HTTPS<\/pre>\n
external_url 'https:\/\/git.nullalo.com:2443'<\/pre>\n
gitlab_git_http_server['listen_network'] = "tcp"\r\ngitlab_git_http_server['listen_addr'] = "localhost:8181"<\/pre>\n
gitlab_workhorse['listen_network'] = "tcp"\r\ngitlab_workhorse['listen_addr'] = "localhost:8181"<\/pre>\n
gitlab_rails['gitlab_email_enabled'] = true\r\ngitlab_rails['gitlab_email_from'] = 'git@git.nullalo.com'\r\ngitlab_rails['gitlab_email_display_name'] = 'Nullalo Git Repository'\r\ngitlab_rails['gitlab_email_reply_to'] = 'noreply@git.nullalo.com'\r\ngitlab_rails['smtp_enable'] = true\r\ngitlab_rails['smtp_address'] = "mail.nullalo.com"\r\ngitlab_rails['smtp_port'] = 25\r\ngitlab_rails['smtp_user_name'] = "info@nullalo.com"\r\ngitlab_rails['smtp_password'] = "yourpassword"\r\ngitlab_rails['smtp_domain'] = "mail.nullalo.com"\r\ngitlab_rails['smtp_authentication'] = "plain"\r\ngitlab_rails['smtp_enable_starttls_auto'] = true\r\ngitlab_rails['smtp_tls'] = false\r\ngitlab_rails['smtp_openssl_verify_mode'] = 'none'<\/pre>\n
git_data_dir "\/var\/www\/vhosts\/nullalo.loc\/git.nullalo.loc\/git-data"<\/pre>\n
gitlab_rails['uploads_directory'] = "\/var\/www\/vhosts\/nullalo.com\/git.nullalo.com\/uploads"<\/pre>\n
gitlab_rails['backup_path'] = "\/var\/www\/vhosts\/nullalo.com\/git.nullalo.com\/backups"\r\ngitlab_rails['backup_keep_time'] = 604800 # Limits backups lifetime to 7 days (604800 seconds)<\/pre>\n
sudo gitlab-ctl reconfigure<\/pre>\n
chmod a+x -R \/var\/www\/vhosts\/nullalo.com\/git.nullalo.com\/git-data\r\nchmod a+x -R \/var\/www\/vhosts\/nullalo.com\/git.nullalo.com\/uploads\r\nchmod a+x -R \/var\/www\/vhosts\/nullalo.com\/git.nullalo.com\/backups<\/pre>\n
Phase\u00a03 \u2013 Plesk Integration<\/h2>\n
upstream gitlab {\r\n server unix:\/var\/opt\/gitlab\/gitlab-rails\/sockets\/gitlab.socket fail_timeout=0;\r\n}<\/pre>\nupstream gitlab {\r\n server unix:\/var\/opt\/gitlab\/gitlab-rails\/sockets\/gitlab.socket fail_timeout=0;\r\n}\r\n\r\nupstream gitlab-git-http-server {\r\n server localhost:8181;\r\n}<\/pre>\nupstream gitlab {\r\n server unix:\/var\/opt\/gitlab\/gitlab-rails\/sockets\/gitlab.socket fail_timeout=0;\r\n}\r\n\r\nupstream gitlab-workhorse {\r\n server localhost:8181;\r\n}<\/pre>\nclient_max_body_size 2048m;<\/pre>\n
client_max_body_size 2048m;<\/pre>\n
\/etc\/init.d\/nginx reload<\/pre>\n
service nginx restart<\/pre>\n
\n![\"gitlab_plesk_01_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_01_en-300x132.png\")
<\/a><\/p>\nlocation \/uploads\/ {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-Ssl on;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation @gitlab {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-Ssl on;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation ~ ^\/(assets)\/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n gzip_static on; # to serve pre-gzipped version\r\n expires max;\r\n add_header Cache-Control public;\r\n}\r\n\r\nlocation ~ \/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n try_files $uri $uri\/index.html $uri.html @gitlab;\r\n}\r\n\r\nerror_page 502 \/502.html;<\/pre>\nlocation \/uploads\/ {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-Ssl on;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation @gitlab {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-Ssl on;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/(info\/refs|git-upload-pack|git-receive-pack)$ {\r\n error_page 418 = @gitlab-git-http-server;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/repository\/archive {\r\n error_page 418 = @gitlab-git-http-server;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/api\/v3\/projects\/.*\/repository\/archive {\r\n error_page 418 = @gitlab-git-http-server;\r\n return 418;\r\n}\r\n\r\nlocation @gitlab-git-http-server {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_buffering off;\r\n\r\n # The following settings only work with NGINX 1.7.11 or newer\r\n #\r\n # # Pass chunked request bodies to gitlab-git-http-server as-is\r\n # proxy_request_buffering off;\r\n # proxy_http_version 1.1;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-Ssl on;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_pass http:\/\/gitlab-git-http-server;\r\n}\r\n\r\nlocation ~ ^\/(assets)\/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n gzip_static on;\r\n expires max;\r\n add_header Cache-Control public;\r\n}\r\n\r\nlocation ~ \/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n try_files $uri $uri\/index.html $uri.html @gitlab;\r\n}\r\n \r\nerror_page 502 \/502.html;<\/pre>\nlocation \/uploads\/ {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation @gitlab {\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n proxy_set_header X-Frame-Options SAMEORIGIN;\r\n\r\n proxy_pass http:\/\/gitlab;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/gitlab-lfs\/objects {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/(info\/refs|git-upload-pack|git-receive-pack)$ {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/repository\/archive {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/api\/v3\/projects\/.*\/repository\/archive {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation ~ ^\/[\\w\\.-]+\/[\\w\\.-]+\/builds\/download {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation ~ \/ci\/api\/v1\/builds\/[0-9]+\/artifacts {\r\n client_max_body_size 0;\r\n error_page 418 = @gitlab-workhorse;\r\n return 418;\r\n}\r\n\r\nlocation @gitlab-workhorse {\r\n client_max_body_size 0;\r\n ## If you use HTTPS make sure you disable gzip compression\r\n ## to be safe against BREACH attack.\r\n # gzip off;\r\n\r\n proxy_read_timeout 300;\r\n proxy_connect_timeout 300;\r\n proxy_redirect off;\r\n\r\n proxy_buffering off;\r\n\r\n # The following settings only work with NGINX 1.7.11 or newer\r\n #\r\n # # Pass chunked request bodies to gitlab-workhorse as-is\r\n # proxy_request_buffering off;\r\n # proxy_http_version 1.1;\r\n\r\n proxy_set_header Host $http_host;\r\n proxy_set_header X-Real-IP $remote_addr;\r\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n proxy_set_header X-Forwarded-Proto $scheme;\r\n\r\n proxy_pass http:\/\/gitlab-workhorse;\r\n}\r\n\r\nlocation ~ ^\/(assets)\/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n gzip_static on; # to serve pre-gzipped version\r\n expires max;\r\n add_header Cache-Control public;\r\n}\r\n\r\nlocation ~ \/ {\r\n root \/opt\/gitlab\/embedded\/service\/gitlab-rails\/public;\r\n try_files $uri $uri\/index.html $uri.html @gitlab;\r\n}\r\n\r\nerror_page 502 \/502.html;<\/pre>\n![\"gitlab_plesk_02_it\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_02_it-300x262.png\")
<\/a><\/p>\nPhase\u00a04 \u2013 GitLab\u00a0Login<\/h2>\n
Username: root<\/pre>\n
Password: 5iveL!fe<\/pre>\n
![\"gitlab_plesk_03_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_03_en-300x170.png\")
<\/a><\/p>\n![\"gitlab_plesk_04_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_04_en-300x170.png\")
<\/a><\/p>\nssh-keygen -t rsa -C "<your email>"<\/pre>\n
cat ~\/.ssh\/id_rsa.pub<\/pre>\n
%USERPROFILE%\\.ssh\\id_rsa.pub<\/pre>\n
![\"gitlab_plesk_05_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_05_en-300x170.png\")
<\/a><\/p>\n![\"gitlab_plesk_06_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_06_en-300x170.png\")
<\/a><\/p>\n
![\"gitlab_plesk_07_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_07_en-300x170.png\")
<\/a><\/p>\n![\"gitlab_plesk_08_en\"](\"\/wp-content\/uploads\/2015\/10\/gitlab_plesk_08_en-300x170.png\")
<\/a><\/p>\n