1. Introduction
    2. Software Catalog basics
    3. Removing the example entities
    4. Creating a software component
    5. Registering a component
    6. Moving towards a production instance
    1. Creating new components using Backstage
    2. Anatomy of a Software Template
    3. Writing new Software Templates
    4. Scaffolder actions
    5. Software Templates at Spotify
    1. Knowledge check

Onboarding Software to Backstage

45 MINS

Moving toward a production instance

You now have the fundamentals in place to start building up a software catalog of your own. But! It’s important to take a moment to reflect on the state of your instance and some additional steps you’ll want to take to move to production:

  • You registered a catalog-info.yaml to a local instance of Backstage, which is connected to a local database. You will likely want to complete the process of registering entities on your real, production instance of Backstage.
  • If you navigate to the entity page of the component you just registered and click on your team’s name under the owner label, you’ll land on an Entity not found error because your team is not yet tracked as a group in the catalog.

Backstage can process catalog info YAML files from most of Source Code hosting providers (GitHub, Gitlab, Bitbucket, etc.) Checkout the Discovery tabs in all the Backstage integrations docs.

You may also be thinking to yourself, this is cool, but I have so many services, how will I onboard all of them? Luckily, for net-new components, you don’t have to worry about onboarding them; in the next section, we’ll cover how Software Templates can be used to automatically register new components as engineers in your organization create new software through Backstage.