Gitlab - Tag - Dimas Maulana

Naming Conventions for Production Environments

Tue, 06 Jun 2023 06:47:00 +0700

Naming conventions are a crucial aspect of software development, providing consistency and clarity in various stages of the development lifecycle. In this article, we will explore the most common naming conventions for production environments, focusing on GitLab CI/CD, GitHub Actions, domain names, branch names, Docker Compose files, and Dockerfile names.

Naming	Common Convention
GitLab CI/CD Convention	prod
GitHub Actions Convention	prod
Domain Names	example.com
Branch Names	main/master
Docker Compose Files	docker-compose.yml
Dockerfile Names	Dockerfile

GitLab CI/CD Convention

In GitLab CI/CD, the convention for naming pipeline stages in production environments commonly involves using “prod” as the keyword. This convention ensures that pipeline stages are easily identifiable and aligned with the production deployment process.

Naming Conventions for Development Environments

Tue, 06 Jun 2023 06:45:00 +0700

Naming conventions play a vital role in software development environments, providing consistency and clarity throughout the development process. In this article, we will explore the most common naming conventions for development environments, covering GitLab CI/CD, GitHub Actions, domain names, branch names, Docker Compose files, and Dockerfile names.

Naming	Common Convention
GitLab CI/CD Convention	dev
GitHub Actions Convention	dev
Domain Names	dev.example.com
Branch Names	dev
Docker Compose Files	docker-compose.dev.yml
Dockerfile Names	Dockerfile.dev

GitLab CI/CD Convention

When working with GitLab CI/CD, the most common convention for naming pipeline stages in development environments is to use “dev” as the keyword. This convention ensures compatibility and alignment with GitLab CI/CD’s pipeline system.

Naming Conventions Stage vs Staging in Software Development

Tue, 06 Jun 2023 06:24:00 +0700

Naming conventions play a crucial role in software development, providing clarity and consistency in various aspects of the development lifecycle. When it comes to naming environments, such as staging, development, and production, there can be variations and debates around the usage of “stage” and “staging.” In this article, we’ll explore the differences and common practices surrounding these terms.

Defining Staging and Development Environments

Naming	Common Convention
GitLab CI/CD Convention	stage
GitHub Actions Convention	staging
Domain Names	staging.example.com
Branch Names	staging
Docker Compose Files	docker-compose.staging.yml
Dockerfile Names	Dockerfile.staging

Staging environments are integral to the software development process, serving as a dedicated space for testing and validation before deploying to production. In most cases, “staging” is commonly used as a noun to represent this environment. It refers to a stable and controlled testing area where developers can ensure their applications are functioning correctly and meet the required standards.

Building and Deploying a React Application to Nginx HTML Folder using GitLab CI with Separate Runners

Fri, 26 May 2023 09:10:00 +0700

Deploying a React application involves building it on one server and deploying it to another. GitLab CI provides a robust solution for automating this process, allowing you to leverage different runners for the build and deployment stages. In this article, we will explore how to utilize GitLab CI to build a React application on a build server and deploy the built source to the Nginx HTML folder on a production server using separate runners.

Deploying Docker Compose Production YAML on GitLab CI/CD

Wed, 17 May 2023 08:01:00 +0700

GitLab CI/CD provides powerful capabilities for automating the deployment of applications. Docker Compose is a popular tool for defining and managing multi-container Docker applications. In this blog post, we’ll explore how to deploy a Docker Compose production YAML file on GitLab CI/CD, even if the runner server and production server are not in the same location.

Prerequisites

Understanding of Docker Compose and GitLab CI/CD concepts.

Step 1: Setting up the Runner

To begin, set up a dedicated runner on the runner server. This runner will handle the execution of the deployment pipeline. Ensure that Docker is installed and properly configured on the runner server.

Git Gitlab Flow

Mon, 28 Mar 2022 06:17:30 +0700

GitLab Flow is a set of best practices for using Git with GitLab, combining elements of Git Flow and GitHub Flow to support various workflows. It emphasizes the use of feature branches for development, with integration to GitLab’s CI/CD pipeline for continuous testing and deployment.

Production Branch

flowchart TB
a-->b-->c-->d-->e
f-->g
c--deployment-->g
g-->h
a[development]
b[development]
c[development]
d[development]
e[development]
f[production]
g[production]
h[production]

Environtment Branches

flowchart LR
a-->b-->c-->d
e-->f-->g-->h
i-->j-->k
a--deploy to\npre-prod-->e
c--deploy to\npre-prod-->g
e--production\ndeployment-->j
a[staging]
b[staging]
c[staging]
d[staging]
e[pre-prod]
f[pre-prod]
g[pre-prod]
h[pre-prod]
i[production]
j[production]
k[production]

Release Branches

flowchart LR
a-->b-->c-->d-->e
a-->f-->g
c-.-chery-pick-.->g
d-->i
a[main]
b[main]
c[main]
d[main]
e[main]
f[2.3-stable]
g[2.3-stable]
i[2.4-stable]

Troubleshooting GitLab Web IDE Error When Trying to Edit a File on a Private GitLab Using Apache Reverse Proxy

Mon, 12 Jul 2021 10:55:46 +0700

GitLab Web IDE is a powerful web-based integrated development environment that allows users to edit, commit, and manage their GitLab projects directly from the browser. However, some users may encounter an error while trying to edit files in the Web IDE when accessing GitLab through an Apache reverse proxy. This article provides a step-by-step solution to resolve the “Error while loading the project data. Please try again” message that appears in this scenario.