Git push Error Message [remote rejected] master -> master

This is an article which is written to handle or to solve the problem generated when someone is using Git version control utility to push either files or folders to a Git repository server. The main purpose for executing ‘push command’ is for updating remote refs along with the associated objects. But eventually pushing those files or folders triggered an error message as shown in the title of this article. So, git utility is utilized to push files or folders and suddenly an error message generated : ‘[remote rejected] master->master’. Below is the actual process happened :

  1. After adding and committing files, folders exist in the folder associated or initialized for Git version control, the last action is to push it to remote Git repository. Below is the command pattern :

Continue reading “Git push Error Message [remote rejected] master -> master”

How to Grant Access to Gitlab Repository

Gitlab repository is a software built for managing git repositories in a centralized server equipped with issue tracking, wiki, etc. Holding the concept of continuous integration and continuous development, the software is quite handy and useful. In this article, there is a specific task which is very important as the first step for managing git repositories using Gitlab. That specific task is a task on how to grant access to Gitlab repository. As we already knew, files or folders are maintained in a certain repository. That specific repository where every each of them have their own rules for user whom can be permitted and for user whom is forbidden to access and perform operations on that repository. So, if a specific repository need to be accessed using a certain user, there is several things need to be done before the actual access to that specific repository can be done. Below is how to grant access to a Git repository for a certain user which is done from Gitlab Git repository management.

1. Access Gitlab Git repository management. Below is the image of Gitlab Git repository management :

How to Grant Access to Gitlab Repository
How to Grant Access to Gitlab Repository

Continue reading “How to Grant Access to Gitlab Repository”

How to Perform Automatic Deployment with Git

This article will discuss the automatic deployment that can be performed using Git version control. This article itself inspired by the writing which is posted in the article titled ‘How to Set Up Automatic Deployment with Git with a VPS’ in this link.

This article will describe the scenario which is a simple scenario and based on the scenario itself, it an be developed later on to be adjusted with the real implementation of the automatic deployment according to the need and the condition associated.

The image depicting the scenario which is going to be described in this article can be shown as follows :

Continue reading “How to Perform Automatic Deployment with Git”

Stop Gitlab via Command Line

In this article, stopping Gitlab’s service will be an action which is an important information to be recognized. Especially if there is a conflict for port usage with another service or application running since the port configuration will have to change Gitlab’s configuration file and going further, the service itself needs to be restarted or to be stop before the service is finally executed to start again.

The command which is used to stop Gitlab’s service is easy and it is actually comprise of short command as shown below :

gitlab-ctl stop

If the command is successfully executed, the output of the above command can be shown as follows :

Continue reading “Stop Gitlab via Command Line”

Check Gitlab Status via Command Line

To be able to check the status of Gitlab, off course the important thing is to have gitlab itself installed. The installation process can be read in the following article after titled ‘Install Gitlab on CentOS 7 via Command Line’ in this link. Another important reference which can be used in an article titled ‘Install Gitlab on Ubuntu via Command Line in the following link.

After installing Gitlab, to be able to run it perfectly, just read the following article which is explaining on how to run Gitlab’s service in the following article titled ‘Start Gitlab via Command Line’. The article can be visited in the following link.

So, the command to view the current status of Gitlab’s service is shown below :

gitlab-ctl status

The output of the above executed command is actually viewed as follows :

Continue reading “Check Gitlab Status via Command Line”

Start Gitlab via Command Line

In this article, starting or running Gitlab is going to be explained so that Gitlab itself can be prepared to receive incoming requests in order to access all Gitlab’s features.

Before accessing Gitlab which is done after Gitlab service has started, the most important thing is having Gitlab itself installed in host, laptop, server or any machine provided for the purpose on running the Gitlab itself. Read the following article titled ‘Install Gitlab on CentOS 7 via Command Line’ for further reference on installing Gitlab in this link. Another article which can be found important as a reference is the article titled ‘Install Gitlab on Ubuntu via Command Line’ in the following link.

The command which is needed to be executed by typing it in the command line or terminal so that Gitlab’s service can be started and running properly is the following one :

Continue reading “Start Gitlab via Command Line”

Install Gitlab in Ubuntu via Command Line

In this article, there will be a full description on how to install Gitlab in Ubuntu using terminal or bash prompt as a Command Line Interface (CLI) as follows :

1. First of all, don’t forget to update the operating system before directly installing  Gitlab. Just type the following command :

apt-get update

The output of the above command’s execution :

root@hostname:~# apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:5 http://archive.canonical.com/ubuntu xenial InRelease
Hit:6 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:7 http://ppa.launchpad.net/gns3/ppa/ubuntu xenial InRelease
Ign:8 http://downloads-distro.mongodb.org/repo/debian-sysvinit dist InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Hit:10 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu xenial InRelease
Hit:11 http://downloads-distro.mongodb.org/repo/debian-sysvinit dist Release
Hit:13 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Hit:14 https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu xenial InRelease
Fetched 102 kB in 2s (44,8 kB/s)
Reading package lists... Done
W: http://downloads-distro.mongodb.org/repo/debian-sysvinit/dists/dist/Release.gpg: Signature by key 492EAFE8CD016A07919F1D2B9ECBEC467F0CEB10 uses weak digest algorithm (SHA1)
root@hostname:~#

2. As root account, execute the following command :

Continue reading “Install Gitlab in Ubuntu via Command Line”