This repository manages Backstage resources. It provides a centralized repository for managing all Backstage configurations, plugins, and customizations. It runs on Google Kubernetes Engine (GKE) and leverages various Google Cloud Platform (GCP) services for scalability and reliability. It depends on google-kubernetes-engine for cluster provisioning and onboarding of namespaces.
The continuous delivery workflows are implemented using GitHub Actions, ensuring testing, building, and deployment of Backstage components.
- Documentation: docs.osinfra.io
- Service Interfaces: github.com
Our focus is on the core fundamental practice of platform engineering, Infrastructure as Code.
Open Source Infrastructure (as Code) is a development model for infrastructure that focuses on open collaboration and applying relative lessons learned from software development practices that organizations can use internally at scale. - Open Source Infrastructure (as Code)
To avoid slowing down stream-aligned teams, we want to open up the possibility for contributions. The Open Source Infrastructure (as Code) model allows team members external to the platform team to contribute with only a slight increase in cognitive load. This section is for developers who want to contribute to this repository, describing the tools used, the skills, and the knowledge required, along with OpenTofu documentation.
See the documentation for setting up a development environment.
Links to documentation and other resources required to develop and iterate in this repository successfully.
A local instance of Backstage can be used to test some of the changes made to the repository. You can go to the application
directory and start the app using the yarn dev command. The yarn dev command will run both the frontend and backend as separate
processes (named [0] and [1]) in the same window.
cd app
yarn dev