Update repository path (#27)

Author: kangasta

.github/workflows/parallel-robot-pipeline.yml

@@ -4,13 +4,13 @@ on:
     branches:
     - main
     paths:
-    - docs/examples/jenkins/parallel-robot-pipeline/**
+    - docs/tutorials/jenkins/parallel-robot-pipeline/**
     - .github/workflows/parallel-robot-pipeline.yml
   pull_request:
     branches:
     - main
     paths:
-    - docs/examples/jenkins/parallel-robot-pipeline/**
+    - docs/tutorials/jenkins/parallel-robot-pipeline/**
     - .github/workflows/parallel-robot-pipeline.yml
 
 jobs:
@@ -21,13 +21,13 @@ jobs:
     - name: Checkout
       uses: actions/checkout@v3
     - name: Build container image
-      working-directory: docs/examples/jenkins/parallel-robot-pipeline/
+      working-directory: docs/tutorials/jenkins/parallel-robot-pipeline/
       run: |
         docker build . --tag rf-screenshot
     - name: Test container image
       run: |
         for browser in chromium firefox; do
-          docker run --rm -v $(pwd)/robot_output:/out -e BROWSER=$browser rf-screenshot -d /out -l none -r none -o $browser.xml -N $browser -v URL:https://kangasta.github.io/cicd-examples/
+          docker run --rm -v $(pwd)/robot_output:/out -e BROWSER=$browser rf-screenshot -d /out -l none -r none -o $browser.xml -N $browser -v URL:https://cicd-tutorials.github.io/cicd-tutorials.net/
         done
     - name: Store logs
       if: always()
@@ -45,13 +45,13 @@ jobs:
         password: ${{ secrets.GITHUB_TOKEN }}
     - name: Push container image to GitHub Container Registry
       if: github.ref == 'refs/heads/main'
-      working-directory: docs/examples/jenkins/parallel-robot-pipeline/
+      working-directory: docs/tutorials/jenkins/parallel-robot-pipeline/
       run: |
         docker build . --target base -t base
 
         for tag in ${{ github.run_number }} latest; do
-          docker tag base ghcr.io/kangasta/robot-browser:$tag
-          docker push ghcr.io/kangasta/robot-browser:$tag
+          docker tag base ghcr.io/cicd-tutorials/robot-browser:$tag
+          docker push ghcr.io/cicd-tutorials/robot-browser:$tag
         done
   process-logs:
     name: Process logs

README.md

@@ -1,6 +1,6 @@
-# CI/CD Examples
+# CI/CD Tutorials
 
-Examples on how to develop CI/CD pipelines and how to configure development environment for working with CI/CD pipelines.
+Tutorials on how to develop CI/CD pipelines and how to configure development environment for working with CI/CD pipelines.
 
 ## Developing
 
@@ -18,5 +18,5 @@ mkdocs serve
 
 ## License
 
-CI/CD Examples is licensed under
+CI/CD Tutorials is licensed under
 <a href="https://creativecommons.org/licenses/by-sa/4.0/" target="_blank" rel="license noopener noreferrer">CC BY-SA 4.0</a>

docs/README.md

@@ -1,6 +1,6 @@
-# CI/CD Pipeline and Tooling Examples
+# CI/CD Pipeline and Tooling Tutorials
 
-This website contains examples on how to develop CI/CD pipelines and how to configure a development environment for working with CI/CD pipelines.
+This website contains tutorials on how to develop CI/CD pipelines and how to configure a development environment for working with CI/CD pipelines.
 
 ## What are CI/CD pipelines?
 
@@ -24,8 +24,8 @@ The CI and CD pipelines are often tightly integrated with each other. Delivery i
 
 ## Installing Docker
 
-Many of the examples provided on this website require Docker and Docker Compose to be installed on your development environment.
+Many of the tutorials provided on this website require Docker and Docker Compose to be installed on your development environment.
 
 See [Get Docker](https://docs.docker.com/get-docker/) for official installation instructions. If you use Docker a lot on a Mac or Windows system, the recommended Docker Desktop is likely a good option for you. Note that, since January 2022, it has required paid subscription, if used for commercial development.
 
-Alternatively, Windows users can [install Docker on top of WSL2](./docker/docker-on-wsl/). For Mac users there are alternatives, such as [Colima](https://github.com/abiosoft/colima), available.
+Alternatively, Windows users can [install Docker on top of WSL2](./tutorials/docker/docker-on-wsl/). For Mac users there are alternatives, such as [Colima](https://github.com/abiosoft/colima), available.

…/examples/docker/docker-on-wsl/README.md …tutorials/docker/docker-on-wsl/README.mddocs/examples/docker/docker-on-wsl/README.md renamed to docs/tutorials/docker/docker-on-wsl/README.md docs/examples/docker/docker-on-wsl/README.md renamed to docs/tutorials/docker/docker-on-wsl/README.md

@@ -6,7 +6,7 @@ description: Tutorial on how to test if Docker-in-Docker service in GitLab CI ac
 
 The recommended way of running Docker commands in a GitLab CI Kubernets runner is to use a service to run Docker-in-Docker container (`docker:dind`). By default the `docker:dind` container pulls container images from Docker Hub without caching. This can cause problems as pulls from Docker Hub are rate-limited.
 
-This example tests how `docker pull ubuntu:24.04` commands consume Docker Hub ratelimit and provides example on how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
+This tutorial tests how `docker pull ubuntu:24.04` commands consume Docker Hub ratelimit and provides example on how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
 
 ## How to check if `docker pull` commands are cached
 
@@ -15,13 +15,13 @@ Create a new GitLab project with `.gitlab-ci.yml` and `scripts/check-docker-hub-
 The `scripts/check-docker-hub-ratelimit.sh` script prints current Docker Hub ratelimit and also writes the result to a file if filename is given as first parameter. See [Docker Hub usage and rate limits](https://docs.docker.com/docker-hub/download-rate-limit/#how-can-i-check-my-current-rate) article in Docker documentation for more details.
 
 ```yaml title="scripts/check-docker-hub-ratelimit.sh"
----8<--- "docs/examples/gitlab-ci/docker-hub-ratelimit/scripts/check-docker-hub-ratelimit.sh"
+---8<--- "docs/tutorials/gitlab-ci/docker-hub-ratelimit/scripts/check-docker-hub-ratelimit.sh"
 ```
 
 The pipeline defined by `.gitlab-ci.yml` tries to pull the same Docker image twice and checks if the rate limit headers are different after first and second pull.
 
 ```yaml title=".gitlab-ci.yml"
----8<--- "docs/examples/gitlab-ci/docker-hub-ratelimit/.gitlab-ci.yml"
+---8<--- "docs/tutorials/gitlab-ci/docker-hub-ratelimit/.gitlab-ci.yml"
 ```
 
 The pipeline should fail, if images are pulled directly from Docker Hub.
@@ -31,8 +31,8 @@ The pipeline should fail, if images are pulled directly from Docker Hub.
 Manifests for configuring pull-through cache and configmap are available in the repository that provides this website.
 
 ```sh
-git clone https://github.com/kangasta/cicd-examples.git
-cd docs/examples/gitlab-ci/docker-hub-ratelimit
+git clone https://github.com/cicd-tutorials/cicd-tutorials.net.git
+cd docs/tutorials/gitlab-ci/docker-hub-ratelimit
 ```
 
 Configure pull-through cache and configmap for GitLab runner by running `kubectl apply -f manifests/`.