Compare commits

..

No commits in common. "1f7b006a64462dfa3019d2b76871729034022b28" and "da85b9197501090673e626fe31bcb58e79372b32" have entirely different histories.

5 changed files with 13 additions and 18 deletions

View File

@ -8,7 +8,7 @@ name: Build and deploy the backend to production
jobs: jobs:
build-and-push: build-and-push:
name: Build and push image name: Build and push image
uses: ./.gitea/workflows/workflow_build-image.yaml uses: ./workflow_build-image.yaml
with: with:
tag: stable tag: stable
secrets: secrets:
@ -16,9 +16,8 @@ jobs:
deploy-prod: deploy-prod:
name: Deploy to production name: Deploy to production
uses: ./.gitea/workflows/workflow_deploy-container.yaml uses: ./workflow_deploy-container.yaml
with: with:
overlay: prod environment: prod
secrets: secrets:
KUBE_CONFIG: ${{ secrets.KUBE_CONFIG }} PACKAGE_REGISTRY_ACCESS: ${{ secrets.KUBE_CONFIG }}
needs: build-and-push

View File

@ -10,17 +10,16 @@ name: Build and deploy the backend to staging
jobs: jobs:
build-and-push: build-and-push:
name: Build and push image name: Build and push image
uses: ./.gitea/workflows/workflow_build-image.yaml uses: ./workflow_build-image.yaml
with: with:
tag: unstable tag: unstable
secrets: secrets:
PACKAGE_REGISTRY_ACCESS: ${{ secrets.PACKAGE_REGISTRY_ACCESS }} PACKAGE_REGISTRY_ACCESS: ${{ secrets.PACKAGE_REGISTRY_ACCESS }}
deploy-prod: deploy-prod:
name: Deploy to staging name: Deploy to production
uses: ./.gitea/workflows/workflow_deploy-container.yaml uses: ./workflow_deploy-container.yaml
with: with:
overlay: stg environment: stg
secrets: secrets:
KUBE_CONFIG: ${{ secrets.KUBE_CONFIG }} PACKAGE_REGISTRY_ACCESS: ${{ secrets.KUBE_CONFIG }}
needs: build-and-push

View File

@ -34,5 +34,5 @@ jobs:
uses: docker/build-push-action@v5 uses: docker/build-push-action@v5
with: with:
context: backend context: backend
tags: git.kluster.moll.re/anydev/anyway-backend:${{ inputs.tag }} tags: git.kluster.moll.re/anydev/anyway-backend:${{intputs.tag}}
push: true push: true

View File

@ -9,11 +9,8 @@ This repository contains the backend code for the application. It utilizes FastA
- Since the application is aimed to be deployed in a container, the `Dockerfile` is provided to build the image. - Since the application is aimed to be deployed in a container, the `Dockerfile` is provided to build the image.
### Deployment ### Deployment
To deploy the backend docker container, we use kubernetes. Modifications to the backend are automatically pushed to a two-stage environment through the CI pipeline. See [deployment/README](deployment/README.md] for further information. To deploy the backend docker container, we use kubernetes. The deployment configuration is located under [https://git.kluster.moll.re/anydev/deployment-backend/](https://git.kluster.moll.re/anydev/deployment-backend/).
The deployment configuration is included as a submodule in the `deployment` directory. The standalone repository is under [https://git.kluster.moll.re/anydev/anyway-backend-deployment/](https://git.kluster.moll.re/anydev/anyway-backend-deployment/).
## Development ## Development
TBD TBD

@ -1 +1 @@
Subproject commit 8927f278f32bf0eca169ce4b13fbde8a4ed57274 Subproject commit 2b8b8390bcf22042ac9c164bab17a44c1291d4bc