Added backstage template for basic python django application #29
No reviewers
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DevFW-CICD/stacks#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "django-backstage-template"
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?
@ -0,0 +10,4 @@backstage.io/kubernetes-namespace: ${{ values.namespace }}argocd/app-name: ${{values.name | dump}}links:- url: https://gitea-192-168-197-3.c-one-infra.de/giteaAdmin/${{ values.name }}Replace the domain name with {{{ .Env.DOMAIN_GITEA }}}
@ -0,0 +27,4 @@annotations:backstage.io/techdocs-ref: dir:.links:- url: https://gitea-192-168-197-3.c-one-infra.de/giteaAdmin/${{ values.name }}same
@ -0,0 +31,4 @@spec:ingressClassName: nginxrules:- host: 192-168-197-3.c-one-infra.deReplace the domain name with {{{ .Env.DOMAIN }}}
@ -0,0 +62,4 @@spec:containers:- name: djangoimage: gitea-192-168-197-3.c-one-infra.de/giteaadmin/${{ values.name }}Replace the domain name with {{{ .Env.DOMAIN_GITEA }}}
@ -0,0 +31,4 @@gitea_password: ${{ secrets.GITEA_PASSWORD }}targetPath: ./- id: fetch-overrides # Apply specific overrides to add features and make modifications for compatibilityI think this can be removed again
@ -0,0 +48,4 @@name: Publish to Giteaaction: publish:giteainput:repoUrl: gitea-192-168-197-3.c-one-infra.de:443/?repo=${{ parameters.name }}same
@ -0,0 +61,4 @@appNamespace: ${{ parameters.name }}argoInstance: in-clusterprojectName: defaultrepoUrl: https://gitea-192-168-197-3.c-one-infra.de:443/giteaAdmin/${{ parameters.name }}same
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.