fix: homogeneous dib lowercase naming

Author: antoinegelloz

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to DIB
+# Contributing to dib
 We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
 
 - Reporting a bug

README.md

@@ -1,12 +1,12 @@
-DIB: Docker Image Builder
+dib: Docker Image Builder
 =========================
 
 ![GitHub release (latest SemVer)](https://img.shields.io/github/v/release/radiofrance/dib?sort=semver)
 ![CI Status](https://img.shields.io/github/actions/workflow/status/radiofrance/dib/qa.yml?label=QA&logo=github-actions&logoColor=fff)
 [![codecov](https://codecov.io/gh/radiofrance/dib/branch/main/graph/badge.svg)](https://codecov.io/gh/radiofrance/dib)
 [![Go Report Card](https://goreportcard.com/badge/github.com/radiofrance/dib)](https://goreportcard.com/report/github.com/radiofrance/dib)
 
-DIB is a tool designed to help build multiple Docker images defined within a directory, possibly having dependencies
+dib is a tool designed to help build multiple Docker images defined within a directory, possibly having dependencies
 with one another, in a single command.
 
 ## Features
@@ -15,20 +15,20 @@ with one another, in a single command.
 - **Dependency Resolution:** Supports dependencies between images. Builds will be queued until all parent images are built, ensuring a smooth and efficient build process.
 - **Test Suites:** Run test suites on images and ensure the tests pass before promoting images to production.
 - **Build Backends:** Multiple build backends supported, including Docker/BuildKit and Kaniko. Choose the backend that best suits your needs.
-- **Execution Environments:** DIB supports multiple executors, allowing you to build images using different environments such as Shell, Docker, or Kubernetes.
+- **Execution Environments:** dib supports multiple executors, allowing you to build images using different environments such as Shell, Docker, or Kubernetes.
 
 ## Documentation
 
-To get started with DIB, please read the [documentation](https://radiofrance.github.io/dib).
+To get started with dib, please read the [documentation](https://radiofrance.github.io/dib).
 
 ## Contributing
 
-We welcome contributions from the community! If you'd like to contribute to DIB, please review our 
+We welcome contributions from the community! If you'd like to contribute to dib, please review our 
 [contribution guidelines](https://github.com/radiofrance/dib/blob/main/CONTRIBUTING.md) for more information.
 
 ## License
 
-DIB is licensed under the [CeCILL V2.1 License](https://cecill.info/licences/Licence_CeCILL_V2.1-en.txt)
+dib is licensed under the [CeCILL V2.1 License](https://cecill.info/licences/Licence_CeCILL_V2.1-en.txt)
 
 ## Support
 

cmd/list.go

@@ -14,8 +14,8 @@ import (
 // listCmd represents the output command.
 var listCmd = &cobra.Command{
 	Use:   "list",
-	Short: "Print list of images managed by DIB",
-	Long:  `dib list will print a list of all Docker images managed by DIB`,
+	Short: "Print list of images managed by dib",
+	Long:  `dib list will print a list of all Docker images managed by dib`,
 	Run: func(cmd *cobra.Command, _ []string) {
 		bindPFlagsSnakeCase(cmd.Flags())
 

docs/backends.md

@@ -1,10 +1,10 @@
 Build Backends
 ==============
 
-The build backend is a software or service responsible for actually building the images. DIB itself is not capable of
+The build backend is a software or service responsible for actually building the images. dib itself is not capable of
 building images, it delegates this part to the build backend.
 
-DIB supports multiple build backends. Currently, available backends are `docker` and `kaniko`. You can select the 
+dib supports multiple build backends. Currently, available backends are `docker` and `kaniko`. You can select the 
 backend to use with the `--backend` option.
 
 **Executor compatibility matrix**
@@ -35,7 +35,7 @@ run on the remote host instead of using the local Docker daemon.
 
 **BuildKit**
 
-If available, DIB will try to use the BuildKit engine to build images, which is faster than the default Docker
+If available, dib will try to use the BuildKit engine to build images, which is faster than the default Docker
 build engine.
 
 ## Kaniko

docs/best-practices.md

@@ -1,9 +1,9 @@
-DIB Best Practices
+dib Best Practices
 ==================
 
 ### Pin dependencies versions in Dockerfiles
 
-As DIB only rebuilds images when something changes in the build context (including the Dockerfile), external 
+As dib only rebuilds images when something changes in the build context (including the Dockerfile), external 
 dependencies should always be pinned to a specific version, so upgrading the dependency triggers a rebuild.
 
 Example:
@@ -13,5 +13,5 @@ RUN apt-get install [email protected]
 
 ### Use .dockerignore
 
-The `.dockerignore` lists file patterns that should not be included in the build context. DIB also ignores those files
+The `.dockerignore` lists file patterns that should not be included in the build context. dib also ignores those files
 when it computes the checksum, so no rebuild is triggered when they are modified.

docs/configuration.md

@@ -1,7 +1,7 @@
 Configuration
 =============
 
-DIB can be configured either by command-line flags, environment variables or configuration file.
+dib can be configured either by command-line flags, environment variables or configuration file.
 
 The command-line flags have the highest priority, then environment variables, then config file. You can set some
 default values in the configuration file, and then override with environment variables of command-line flags.
@@ -15,7 +15,7 @@ dib build --registry-url=gcr.io/project
 
 ### Environment variables
 
-DIB auto-discovers configuration from environment variables prefixed with `DIB_`, followed by the capitalized, 
+dib auto-discovers configuration from environment variables prefixed with `DIB_`, followed by the capitalized, 
 snake_cased flag name.
 
 Example:
@@ -26,7 +26,7 @@ dib build
 
 ### Configuration file
 
-DIB uses a YAML configuration file in addition to command-line arguments. It will look for a file names `.dib.yaml`
+dib uses a YAML configuration file in addition to command-line arguments. It will look for a file names `.dib.yaml`
 in the current working directory. You can change the file location by setting the `--config` (`-c`) flag.
 
 The YAML keys are equivalent to the flag names, in snake_case.

docs/documentation.md

@@ -4,7 +4,7 @@ Documentation
 The documentation is generated with [`mkdocs`](https://www.mkdocs.org/). It generates a static website in plain HTML 
 from the Markdown files present in the `docs/` directory.
 
-We also use the [Cobra](https://github.com/spf13/cobra) built-in documentation generator for DIB commands.
+We also use the [Cobra](https://github.com/spf13/cobra) built-in documentation generator for dib commands.
 
 ## Local Setup
 

docs/examples/config/reference.yaml

@@ -4,13 +4,13 @@ log_level: info
 
 # URL of the registry where the images should be stored.
 #
-# DIB will use the local docker configuration to fetch metadata about existing images. You may use the DOCKER_CONFIG
+# dib will use the local docker configuration to fetch metadata about existing images. You may use the DOCKER_CONFIG
 # environment variable to set a custom docker config path.
 # See the official Docker documentation (https://docs.docker.com/engine/reference/commandline/cli/#configuration-files).
 # The build backend must also be authenticated to have permission to push images.
 registry_url: registry.example.org
 
-# The placeholder tag DIB uses to mark which images are the reference. Defaults to "latest".
+# The placeholder tag dib uses to mark which images are the reference. Defaults to "latest".
 # Change this value if you don't want to use "latest" tags, or if images may be tagged "latest" by other sources.
 placeholder_tag: latest
 

docs/executors.md

@@ -1,7 +1,7 @@
 Executors
 =========
 
-DIB supports multiple build executors. An executor is a platform able to run image builds and tests.
+dib supports multiple build executors. An executor is a platform able to run image builds and tests.
 Unlike the build backends which can be explicitely chosen, the executor is automatically selected depending on the type 
 of operation (build, test), and the executors configured in the configuration file.
 
@@ -24,7 +24,7 @@ Runs commands in a docker container, using the `docker run` command.
 ## Kubernetes
 
 Creates pods in a kubernetes cluster, using the kubernetes API. 
-DIB uses the current kube context, please make do
+dib uses the current kube context, please make do
 
 See an example configuration in the 
 [configuration reference](configuration-reference.md) section.

docs/extra-tags.md

@@ -1,10 +1,10 @@
 Extra Tags
 ==========
 
-Images managed by DIB will get tagged with the human-readable version of the computed hash. This is not very convenient
+Images managed by dib will get tagged with the human-readable version of the computed hash. This is not very convenient
 in some cases, for instance if we want to tag an image with the explicit version of the contained software.
 
-DIB allows additional tags to be definedusing a label in the Dockerfile:
+dib allows additional tags to be definedusing a label in the Dockerfile:
 ```dockerfile
 LABEL dib.extra-tags="v1.0.0,v1.0,v1"
 ```