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

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do
Post a Comment
Read more

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv
6 comments
Read more

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You
5 comments
Read more