Deploying with Deployer and GitLab Pipelines

Deploying with Deployer and GitLab Pipelines This post explains how to set up a deployment workflow for a project using Deployer and GitLab Pipelines, including steps to build a new release, package it, and deploy it to a server via SSH. The article outlines creating a custom Docker image, configuring SSH access, and defining a .gitlab-ci.yml file to automate the deployment process. It serves as a guide for developers looking to implement similar workflows. https://lnkd.in/eXf6ug_j

GitOps changed how we deploy to Kubernetes. Instead of running kubectl commands manually, we now commit YAML to Git and ArgoCD handles the rest. Every deployment is versioned, auditable, and reversible. Here is our production setup: ArgoCD watches our Gitea repo. On every push to main, it compares desired state vs actual state. If they differ, it syncs automatically. Benefits we have seen: - Zero-downtime deployments

GitOps changed how we deploy to Kubernetes. Instead of running kubectl commands manually, we now commit YAML to Git and ArgoCD handles the rest. Every deployment is versioned, auditable, and reversible. Here is our production setup: ArgoCD watches our Gitea repo. On every push to main, it compares desired state vs actual state. If they differ, it syncs automatically. Benefits we have seen: - Zero-downtime deployments

Helm is an essential tool to know when working with Kubernetes. Seeing hands-on examples that walk through the full lifecycle: adding repos, inspecting charts, deploying NGINX ingress, and configuring real overrides always helps to learn. This guide doesn't just show the happy path, it walks through pushing a bad image tag, watching pods fail, and then using Helm's rollback to recover cleanly. This mirrors how most people will likely experience using Helm (or other tools) which helps to make the lesson stick. Shivam Soni shows clear command breakdowns and no unnecessary abstraction. If you are getting started with Helm or want a refresher on release versioning and rollback mechanics, this is a clean and well-structured read worth checking out. https://lnkd.in/eAwFxdYK

After seeing the same situation over and over, a sudden failing GitLab pipeline, because a token expired... ... here's an article that describes how to discover access tokens and automate GitLab access token rotation

New preview features around Fabric Git Integration were just announced. Selective branch out and viewing code changes in the service! These are nice low-code features for getting folks acquainted with version control. https://lnkd.in/d22FpG3y

✨ Best Self-Hosted Tools for Developers in 2026 Discover the best self-hosted tools for developers, including Git, CI/CD, Docker, monitoring, and deployment platforms. Git Hosting: Gitea or GitLab Self-Managed CI/CD: Built-in Git CI or Argo CD Deployment: Coolify Container Registry: Harbor Observability: Prometheus + Grafana + Loki + OpenTelemetry Authentication: authentik Documentation: BookStack Developer Portal: Backstage Backend Platform: Supabase https://lnkd.in/gCkVzCVq

GitHub Actions vs GitLab CI/CD: Complete CI/CD Comparison (2026) Created by 楊東霖 Choosing the right CI/CD platform is one of the highest-leverage decisions a development team makes. It shapes how you test, build, and ship software every single day. In 2026, the two dominant platforms — GitHub Actions and GitLab CI/CD — have both matured into powerful, production-ready systems... link https://lnkd.in/eqsbxntm pubDate Fri, 20 Mar 2026 03:52:03 +0000

Artie now supports OpenTofu This lets teams define pipelines, sources, and destinations in code, version them in Git, and deploy changes across environments using tofu plan and tofu apply. Why this matters: - Manage pipeline configuration the same way you manage infrastructure - Promote changes cleanly from dev → staging → prod - Reduce configuration drift across environments If your team has moved from Terraform to OpenTofu, you can now manage Artie the same way. Change log in the comments

You need to implement continuous delivery of infrastructure changes while ensuring minimal downtime. Question: How do you integrate Terraform with a CI/CD pipeline to achieve this? Answer: Pipeline Setup: Integrate Terraform commands into your CI/CD tool (e.g., Jenkins, GitLab CI). Infrastructure Testing: Use terraform plan in a staging environment before applying changes to production. Blue-Green Deployments: Implement blue-green deployments to minimize downtime. Deploy changes to a "blue" environment, test, and switch traffic using a load balancer. Example: stages: - plan - apply plan: script: - terraform init - terraform plan -out=tfplan apply: script: - terraform apply "tfplan" Monitoring and Rollback: Implement monitoring and alerting to detect issues post-deployment. Use version control to rollback changes if necessary.