From 3d54c0428c7672e1c307d226dec3c4d55b9ea3b8 Mon Sep 17 00:00:00 2001
From: Olivier El Mekki <olivier@el-mekki.com>
Date: Mon, 10 Jul 2023 11:59:25 +0200
Subject: [PATCH] ADD use Gtilab's registry to host image

---
 .gitlab-ci.yml | 10 ++++++++++
 README.md      |  8 ++++++++
 2 files changed, 18 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 00c9ba1..3cc9634 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -4,9 +4,19 @@ services:
 
 stages:
 - test
+- build
 
 testing_image:
   stage: test
   script:
     - docker build -t pg-350d .
     - ./test.sh
+
+upload_image:
+  stage: build
+  variables:
+    IMAGE_TAG: $CI_REGISTRY_IMAGE:15.3
+  script:
+    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
+    - docker build -t $IMAGE_TAG .
+    - docker push $IMAGE_TAG
diff --git a/README.md b/README.md
index 992efb9..6e48659 100644
--- a/README.md
+++ b/README.md
@@ -18,6 +18,14 @@ editing this dockerfile.
 The cube extension, which you'll use to perform operations on vectors, has
 a hard limit of 100 dimensions per vector.
 
+## Download
+
+A built image is available on Gitlab's registry. You can pull it this way:
+
+```
+docker pull registry.gitlab.com/oelmekki/postgres-350d:15.3
+```
+
 ## Is it safe?
 
 Patching the hardcoded limit is [the recommended way in postgres