https://github.com/q-shift/qshift-templates

Backstage templates for the Qshift demo
https://github.com/q-shift/qshift-templates

Last synced: 7 days ago
JSON representation

Backstage templates for the Qshift demo

• Host: GitHub
• URL: https://github.com/q-shift/qshift-templates
• Owner: q-shift
• License: apache-2.0
• Created: 2024-02-02T08:41:54.000Z (9 months ago)
• Default Branch: main
• Last Pushed: 2024-05-09T15:27:39.000Z (6 months ago)
• Last Synced: 2024-08-02T15:10:47.309Z (3 months ago)
• Language: Smarty
• Size: 484 KB
• Stars: 1
• Watchers: 1
• Forks: 3
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Backstage templates

- Templates to be used on a local Kubernetes cluster. See instructions [here](https://github.com/ch007m/package-backstage)

- Quarkus templates developed for the initiative QShift:

  - [Quarkus-application](qshift/templates/quarkus-application)

    This template allows to scaffold a Quarkus application using `code.quarkus.io` and to enrich the project with `starter` code. 

  

    If you select as database `Postgresql` and the extensions: `RESTeasy reactive`, `RESTeasy reactive jackson`, `REST resources for Hibernate ORM with Panache`, then the Quarkus application deployed on the OpenShift cluster will access a local Postgresql DB to store some `My-entity` records.

 

    You will be able to access the application using the route: `https://my-quarkus-app-native-deploy-quarkus-deploy-./my-entity`

    

    **Important**: The recommendation is to delete the PVC of the postgres DB after played with a project scaffolded as the PVC

    is not deleted OOTB when we remove the ArgoCD Application installing the DB using Bitnami Helm chart. If you don't do that, as the generated password

    to access the DB changes, then you will get an authentication issue !

  - Quarkus-quickstart: Not up to date !!