anydev/anyway
0
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

backend - towards a better gitops deploy strategy #70

Open
remoll wants to merge 11 commits from feature/staging-deployment-on-pr into main
pull from: feature/staging-deployment-on-pr
merge into: anydev:main
Conversation 1 Commits 11 Files Changed 11 +60 -66
remoll commented 2025-10-13 15:29:12 +00:00
Owner
Copy Link

This PR paves the way towards a cleaner way of handling backend deployments, both in staging and in prod. It also addresses a few other DX improvements:

  • (most centrally:) the deployment of the production backend is now handled by argocd. This means that an update to the tag (+ a scan by renovate) will trigger an update to the deployment under https://git.kluster.moll.re/anydev/anyway-backend-deployment. This repository is being watched by argocd and will update the deployment automatially.
  • the deployment of staging instances of the backend is also handled by argocd. Upon each PR, a whole new deployment (with a separate container, service, ingress...) is spun up and can be tested extensively, indepedently of all the other currently open PRs. When the PR is merged/closed the staging version is torn down.
  • switched to envFile in the local python vs code run config. (addresses issues raised in #60 ) - no more pesky load_dotenv()
  • added necessary shell files to develop the whole stack on nix
This PR paves the way towards a cleaner way of handling backend deployments, both in staging and in prod. It also addresses a few other DX improvements: - [x] (most centrally:) the deployment of the production backend is now handled by argocd. This means that an update to the tag (+ a scan by renovate) will trigger an update to the deployment under https://git.kluster.moll.re/anydev/anyway-backend-deployment. This repository is being watched by argocd and will update the deployment automatially. - [x] the deployment of staging instances of the backend is also handled by argocd. Upon each PR, a whole new deployment (with a separate container, service, ingress...) is spun up and can be tested extensively, indepedently of all the other currently open PRs. When the PR is merged/closed the staging version is torn down. - [x] switched to `envFile` in the local python vs code run config. (addresses issues raised in #60 ) - no more pesky `load_dotenv()` - [x] added necessary shell files to develop the whole stack on `nix`
remoll added 1 commit 2025-10-13 15:29:13 +00:00
towards a better gitops deploy strategy
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Failing after 38s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m20s
Details
Run testing on the backend code / Build (pull_request) Failing after 27m28s
Details
c11faee824
remoll added 1 commit 2025-10-13 16:03:48 +00:00
add missing dollar sign
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Failing after 36s
Details
Run linting on the backend code / Build (pull_request) Successful in 2m46s
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
fe2a0cf1d5
remoll added 1 commit 2025-10-13 16:05:35 +00:00
since branch names may contain slashes and other special chars they are not suitable for tag names. only use the hash
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m54s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m19s
Details
Run testing on the backend code / Build (pull_request) Failing after 24m59s
Details
d1cbf972fe
remoll added 1 commit 2025-10-14 09:21:35 +00:00
remove backend deployment submodule
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 2m12s
Details
Run linting on the backend code / Build (pull_request) Successful in 1m0s
Details
Run testing on the backend code / Build (pull_request) Failing after 23m1s
Details
e14900e9f0
remoll added 1 commit 2025-10-14 12:11:25 +00:00
add a comment containing additional deployment information
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m23s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m20s
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
41d076e3d6
remoll closed this pull request 2025-10-14 12:24:05 +00:00
remoll reopened this pull request 2025-10-14 12:25:29 +00:00
remoll added 2 commits 2025-10-14 12:32:08 +00:00
add a comment containing additional deployment information
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m23s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m20s
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
41d076e3d6
add a comment containing additional deployment information
Some checks failed
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 2m7s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 21s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m35s
Details
708c07cf49
remoll added 1 commit 2025-10-14 12:50:33 +00:00
try with correct url?
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m49s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 21s
Details
Run linting on the backend code / Build (pull_request) Has been cancelled
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
219cfcf1a6
remoll added 1 commit 2025-10-14 14:02:33 +00:00
try using the gitea cli instead
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 2m15s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 25s
Details
Run linting on the backend code / Build (pull_request) Successful in 4m7s
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
ec3ed054fd
remoll added 1 commit 2025-10-14 14:18:38 +00:00
try whithout body flag
Some checks failed
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m25s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 4s
Details
Run linting on the backend code / Build (pull_request) Successful in 3m31s
Details
d8c6bfcda0
remoll added 1 commit 2025-10-14 15:00:13 +00:00
more tea attempts
Some checks failed
Run linting on the backend code / Build (pull_request) Has been cancelled
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m56s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 14s
Details
89c5fc9370
remoll added 1 commit 2025-10-14 15:15:13 +00:00
maybe like this?
Some checks failed
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
Run linting on the backend code / Build (pull_request) Has been cancelled
Details
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 2m32s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Failing after 4s
Details
aeed9c7dc9
remoll added 1 commit 2025-10-14 15:19:30 +00:00
man what?
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m35s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Successful in 5s
Details
Run linting on the backend code / Build (pull_request) Has been cancelled
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
71c7325370
gitea-actionsbot commented 2025-10-14 15:21:12 +00:00
Copy Link

The backend has been deployed to staging with url https://pr-70.anyway-stg.anydev.info. Check the deployment status in ArgoCD:

App Status

The backend has been deployed to staging with url https://pr-70.anyway-stg.anydev.info. Check the deployment status in ArgoCD: [![App Status](https://argocd.kluster.moll.re/api/badge?name=anydev-anyway-backend-stg-pr-70&revision=true&showAppName=true)](https://argocd.kluster.moll.re/applications/anydev-anyway-backend-stg-pr-70)
Some checks failed
Build and deploy the backend to staging / Build and push image (pull_request) Successful in 1m35s
Details
Build and deploy the backend to staging / Add a comment to the PR to notify about the deployment (pull_request) Successful in 5s
Details
Run linting on the backend code / Build (pull_request) Has been cancelled
Details
Run testing on the backend code / Build (pull_request) Has been cancelled
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/staging-deployment-on-pr:feature/staging-deployment-on-pr
git checkout feature/staging-deployment-on-pr
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kscheidecker remoll renovate
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anydev/anyway#70
No description provided.
Delete Branch "feature/staging-deployment-on-pr"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?