📄️ Catalog
The Software Catalog is the central hub of DevPortal — a registry of software components, APIs, infrastructure resources, systems, groups, and users in your organization. It is built on the Backstage catalog model described at Backstage software catalog.
📄️ Composing a Portal
A DevPortal installation is a service catalog and a way to create projects from templates. Teams register services, create new ones from templates, and browse the software landscape. Plugin composition lets developers see pod status, trigger deployments, check code quality, and browse dashboards from service pages. A 3.x portal combines four parts: the image with the core, the chart, the catalog index image behind the default plugins and Marketplace, and the configuration fragments.
🗃️ API Catalog
2 items
📄️ Software Templates
How to Create Components Using Templates in the Developer Portal
📄️ Dynamic Plugins
Dynamic plugins add Backstage plugins to the portal without rebuilding the container image. The portal installs them at startup from digest-pinned OCI references and loads their code from the plugin root directory.
📄️ Configuration Hierarchy
Backstage merges every --config file in the order it is passed on the command line. The merge is deep for objects and last-wins for single values: when two files set the same key, the later file wins. A list in a later file replaces the same list from an earlier file instead of merging with it. DevPortal 3.x assembles that --config chain from a base file plus a fixed set of product fragments.
📄️ Writing Templates
This guide covers how to author a Backstage software template — the YAML entity that drives the scaffolder wizard. It assumes you know how to run a template as a developer. If you want to run templates, see Software Templates.
📄️ Available Actions
Actions are functions registered in the scaffolder backend. You invoke them by id inside a template step. This page lists the 16 actions on a default install, all built into @backstage/plugin-scaffolder-backend.