Update repository.mdx (#4877)

Dot missing at the end of the docker build command

Author: FloBLeman

docs/docs/guides/repository.mdx

@@ -305,7 +305,7 @@ This guide makes the assumption that you have saved the CA certificate file as `
 Next we will have to create a Dockerfile. The file should be saved as `Dockerfile` in the same directory as the directory containing the CA certificate you want to install.
 
 ```dockerfile
-ARG INFRAHUB_VERSION=0.16.0
+ARG INFRAHUB_VERSION=latest
 FROM registry.opsmill.io/opsmill/infrahub:${INFRAHUB_VERSION}
 
 COPY mycacertificate.crt /usr/local/share/ca-certificates/
@@ -315,18 +315,18 @@ RUN update-ca-certificates
 We then have to build a Docker image from the Dockerfile. We can do this by executing this command
 
 ```shell
-INFRAHUB_VERSION=0.16.0 && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION}
+INFRAHUB_VERSION=latest && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION} .
 ```
 
-This will build a custom docker image and tag it as `custom/infrahub:0.16.0`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
+This will build a custom docker image and tag it as `custom/infrahub:latest`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
 
 As a last step we have to create a `docker-compose.override.yml` file with the following contents in the `development` directory of your clone of the Infrahub repository.
 
 ```yaml
 ---
 services:
   task-worker:
-    image: custom/infrahub:0.16.0
+    image: custom/infrahub:latest
 ```
 
 A development environment can then be spun up with `invoke demo.start` command as, explained in the [Installing Infrahub guide](/guides/installation).
@@ -350,7 +350,7 @@ In this process we will have to build a custom docker image. This docker image w
 We will have to create a Dockerfile, that should be saved as `Dockerfile` on your local filesystem.
 
 ```dockerfile
-ARG INFRAHUB_VERSION=0.16.0
+ARG INFRAHUB_VERSION=latest
 FROM registry.opsmill.io/opsmill/infrahub:${INFRAHUB_VERSION}
 
 RUN git config --global http.sslVerify "false"
@@ -359,18 +359,18 @@ RUN git config --global http.sslVerify "false"
 We then have to build a Docker image from the Dockerfile. We can do this by executing this command
 
 ```shell
-INFRAHUB_VERSION=0.16.0 && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION}
+INFRAHUB_VERSION=latest && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION} .
 ```
 
-This will build a custom docker image and tag it as `custom/infrahub:0.16.0`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
+This will build a custom docker image and tag it as `custom/infrahub:latest`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
 
 As a last step we have to create a `docker-compose.override.yml` file with the following contents in the `development` directory of your clone of the Infrahub repository.
 
 ```yaml
 ---
 services:
   task-worker:
-    image: custom/infrahub:0.16.0
+    image: custom/infrahub:latest
 ```
 
 A development environment can then be spun up with `invoke demo.start` command as, explained in the [Installing Infrahub guide](/guides/installation).
@@ -394,7 +394,7 @@ In this process we will have to build a custom docker image. This docker image w
 We will have to create a Dockerfile, that should be saved as `Dockerfile` on your local filesystem. In the Dockerfile you will have to adapt the URL for the proxy to your environment. Replace `user:password` with the username and password you have to use for the proxy, if required. Replace the FQDN `internal.proxy` to the FQDN of the proxy and modify the port, if required.
 
 ```dockerfile
-ARG INFRAHUB_VERSION=0.16.0
+ARG INFRAHUB_VERSION=latest
 FROM registry.opsmill.io/opsmill/infrahub:${INFRAHUB_VERSION}
 
 RUN git config --global http.proxy http://user:[email protected]:8080
@@ -403,18 +403,18 @@ RUN git config --global http.proxy http://user:[email protected]:8080
 We then have to build a Docker image from the Dockerfile. We can do this by executing this command
 
 ```shell
-INFRAHUB_VERSION=0.16.0 && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION}
+INFRAHUB_VERSION=latest && docker build --build-arg INFRAHUB_VERSION=$INFRAHUB_VERSION -f Dockerfile -t custom/infrahub:${INFRAHUB_VERSION} .
 ```
 
-This will build a custom docker image and tag it as `custom/infrahub:0.16.0`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
+This will build a custom docker image and tag it as `custom/infrahub:latest`. You can change the version by changing the version we set in the `INFRAHUB_VERSION` shell variable and you can change the tag to you own preference.
 
 As a last step we have to create a `docker-compose.override.yml` file with the following contents in the `development` directory of your clone of the Infrahub repository.
 
 ```yaml
 ---
 services:
   task-worker:
-    image: custom/infrahub:0.16.0
+    image: custom/infrahub:latest
 ```
 
 A development environment can then be spun up with `invoke demo.start` command as, explained in the [Installing Infrahub guide](/guides/installation).