This blog’s source of truth and CI live on GitLab. The public site is served from GitHub Pages at devopstales.github.io. Hugo builds in a container, the job writes into a separate Pages repository, and readers never see GitLab’s job logs—only the static tree.
Roadster’s default sidebar search sends queries to Google (or DuckDuckGo) with a site filter. That works until the corpus is large and you want typo tolerance, facets by section/tags, and results that stay on your domain. Algolia hosts the index; Hugo emits a JSON dump at build time; atomic-algolia pushes only the diff from GitLab CI after hugo succeeds.
Install GitLab CE with custom PostgreSQL and Nginx proxy.
FluxCD Operator brings a simplified management experience and a native web UI for monitoring your GitOps workflows. This guide walks you through migrating an existing FluxCD installation to the Operator pattern with UI enabled, while maintaining GitLab as your Git source.
One of the most common use case is to build a Docker image with Gitlab. In a previous post we used dedicated docker runners for this job. But howe can we build images in a Kubernetes runner? In this post we well se this.
One of the most common use case is to build a Docker image with Gitlab. In this post I will show you how to set up Docker builds in CI.
In this post I will show you how you can pass artifacts between in gitlab CI.
In this post I will show you the basics of using gitlab as a Continuous Integration and Continuous Deployments (CI/CD) tool.
I this blog post I will show you how you can validate your kubernetes objects, helm charts, images at CI/CD.
In this post I will show you how how you can create a K8S cluster with Terraform and GitlabCI.