Skip to main content

Quick guide to install GitLab (Community Edition)

A quick tutorial on how to install GitLab (https://about.gitlab.com/) CE (Community Edition). The steps described in this post have been verified and tested on Red Hat Linux Server 6.x 64-bit, but they should work also on Red Hat 7.x, CentOS 6.x+, Oracle 6.x+ and Scientific Linux 6.x+ distributions.
 

Installation.

We are going to use the Omnibus package. It includes almost all of the packages needed, but OpenSSH and Postfix. These are the installation steps (all of the commands below need to be issued with a user having root privileges.):
 - Check whether the following prerequisites are present in the system: OpenSSH Server (http://www.openssh.com/) and Postfix (http://www.postfix.org/). If not, before proceeding in the GitLab installation, please install them following the official documentation and the specific steps for your Linux distribution.
 - Download the Omnibus package (the command below is for CentOS 6.x/Red Hat 6.x/Oracle/Scientific Linux distributions and refers to the release 8.3.4):
wget https://packages.gitlab.com/gitlab/gitlab-ce/packages/el/6/gitlab-ce-8.3.4-ce.0.el6.x86_64.rpm/download
 - Install it manually through RPM:
    rpm -i gitlab-ce-8.3.4-ce.0.el6.x86_64.rpm
 - Reconfigure it:
    gitlab-ctl reconfigure
 - Check that all its services are running:
    gitlab-ctl status
   If everything is fine you should see an output like this:
        run: gitlab-workhorse: (pid 42049) 69s; run: log: (pid 41915) 110s
        run: logrotate: (pid 41933) 102s; run: log: (pid 41932) 102s
        run: nginx: (pid 41922) 108s; run: log: (pid 41921) 108s
        run: postgresql: (pid 41798) 135s; run: log: (pid 41797) 135s
        run: redis: (pid 41712) 146s; run: log: (pid 41711) 146s
        run: sidekiq: (pid 41905) 112s; run: log: (pid 41904) 112s
        run: unicorn: (pid 41873) 114s; run: log: (pid 41872) 114s

First login.

 - Connect to the UI through a web browser. Example:
    http://my-hostname/
 - Use the default credentials created at installation time to login:
    username:    root
    password:    5iveL!fe
    Please note that this is the standard GitLab user created at installation time and not the root user of the machine.
 - You will be asked to change the password.
 - Log in again using the new password.
Now you can start to create users, groups and projects.
Labels:

Comments

Post a Comment

Popular posts from this blog

Turning Python Scripts into Working Web Apps Quickly with Streamlit

 I just realized that I am using Streamlit since almost one year now, posted about in Twitter or LinkedIn several times, but never wrote a blog post about it before. Communication in Data Science and Machine Learning is the key. Being able to showcase work in progress and share results with the business makes the difference. Verbal and non-verbal communication skills are important. Having some tool that could support you in this kind of conversation with a mixed audience that couldn't have a technical background or would like to hear in terms of results and business value would be of great help. I found that Streamlit fits well this scenario. Streamlit is an Open Source (Apache License 2.0) Python framework that turns data or ML scripts into shareable web apps in minutes (no kidding). Python only: no front‑end experience required. To start with Streamlit, just install it through pip (it is available in Anaconda too): pip install streamlit and you are ready to execute the working de...
14 comments
Read more

Load testing MongoDB using JMeter

Apache JMeter ( http://jmeter.apache.org/ ) added support for MongoDB since its 2.10 release. In this post I am referring to the latest JMeter release (2.13). A preliminary JMeter setup is needed before starting your first test plan for MongoDB. It uses Groovy as scripting reference language, so Groovy needs to be set up for our favorite load testing tool. Follow these steps to complete the set up: Download Groovy from the official website ( http://www.groovy-lang.org/download.html ). In this post I am referring to the Groovy release 2.4.4, but using later versions is fine. Copy the groovy-all-2.4.4.jar to the $JMETER_HOME/lib folder. Restart JMeter if it was running while adding the Groovy JAR file. Now you can start creating a test plan for MongoDB load testing. From the UI select the MongoDB template ( File -> Templates... ). The new test plan has a MongoDB Source Config element. Here you have to setup the connection details for the database to be tested: The Threa...
40 comments
Read more

Evaluating Pinpoint APM (Part 1)

I started a journey evaluating Open Source alternatives to commercial New Relic and AppDynamics tools to check if some is really ready to be used in a production environment. One cross-platform Application Performance Management (APM) tool that particularly caught my attention is Pinpoint . The current release supports mostly Java applications and JEE application servers and provides support also for the most popular OS and commercial relational databases. APIs are available to implement new plugins to support specific systems. Pinpoint has been modeled after Google Dapper and promises to install agents without changing a single line of code and mininal impact (about 3% increase in resource usage) on applications performance. Pinpoint is licensed under the Apache License, Version 2.0 . Architecture Pinpoint has three main components:  - The collector: it receives monitoring data from the profiled applications. It stores those information in HBase .  - The web UI: the f...
4 comments
Read more