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 :
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 :
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 :
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 :
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 :
If the command is successfully executed, the output of the above command can be shown as follows :
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 :
The output of the above executed command is actually viewed as follows :
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 :