diff --git a/.github/workflows/dev-frontend.yml b/.github/workflows/dev-frontend.yml
new file mode 100644
index 0000000..f260565
--- /dev/null
+++ b/.github/workflows/dev-frontend.yml
@@ -0,0 +1,13 @@
+name: Dev frontend workflow
+
+on:
+  push:
+    branches:
+      - 'dev/frontend@**'
+  workflow_dispatch:
+
+jobs:
+  trigger-frontend-ci:
+    uses: ./.github/workflows/frontend-ci.yml
+
+    # cd part use watchtower to update the container will be changed to a more clever way once we scale up our services
\ No newline at end of file
diff --git a/.github/workflows/frontend-ci.yml b/.github/workflows/frontend-ci.yml
new file mode 100644
index 0000000..57fb898
--- /dev/null
+++ b/.github/workflows/frontend-ci.yml
@@ -0,0 +1,58 @@
+name: Build and upload docker image of frontend to GHCR 
+
+on:
+  workflow_dispatch:
+  workflow_call:
+
+
+
+# Configures this workflow to run every time a change is pushed to the branch called `release`.
+
+# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository_owner }}/pastexam/frontend
+
+# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
+jobs:
+  build-and-push-image:
+    runs-on: ubuntu-latest
+    # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
+    permissions:
+      contents: read
+      packages: write
+      attestations: write
+      id-token: write
+      # 
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      - name: Log in to the Container registry
+        uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          tags: |
+            type=raw,value=latest
+            type=ref,event=branch
+            type=ref,event=tag
+      # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
+      # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
+      # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
+      - name: Build and push Docker image
+        id: push
+        uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
+        with:
+          context: ./frontend
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+      
+      
diff --git a/watchtower/compose.yml b/watchtower/compose.yml
new file mode 100644
index 0000000..7d4eef0
--- /dev/null
+++ b/watchtower/compose.yml
@@ -0,0 +1,8 @@
+services:
+  watchtower:
+    image: containrrr/watchtower
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+    command: 
+      --interval 10 --cleanup
+    restart: always