avaliasystems/dx-hub

DX Hub: ignite your Backstage Developer Portal

dx-hub's Issues

Add an easy way to change the color scheme (theme) for Docker users

For people running DX Hub with yarn, it is pretty easy to customize the provided theme and to change the color scheme (to use the organization branding).

It would be interesting to allow people who run DX Hub via Docker and don't want to update the code to achieve the same result.

Investigate use of docker caching in github actions

See:

• https://docs.docker.com/build/ci/github-actions/cache/#cache-mounts
• https://github.com/reproducible-containers/buildkit-cache-dance

Add an easy way to add your organization name / logo, also for Docker users

For people planning a demo at their organization, it would be interesting to have an easy way to add their own name or logo. We need to update the page layout and use a mounted volume.

Create more synthetic data for the demo catalog

At the moment, we only have a handful of entities in the catalog. It would be good to have a larger organization (teams and people), more software assets (components, systems, domains) and APIs. We could use public open source orgs and projects.

Add an easy way to replace the "hero" images in the demo pages

The demo page uses images created at Avalia Systems, that match our theme and color scheme. For people doing demos at their orgs, it might make sense to replace these with org-specific images.

Improve development workflow for DX Hub plugins

Context

The initial version of this repo was not designed to release the individual plugins we will add to DX Hub over time. We want to make these plugins available to Backstage adopters and therefore need a way to publish them via the central npm registry.

This question fits into the broader context of managing this repo as a "mono repo". Looking at the evolution and the current state of these repos, we see that there is no single approach:

• Some organizations have migrated to yarn 3, while others are still using yarn 1
• Some organizations have dropped lerna while moving to yarn 3
• Some organizations have upgraded to a more recent version of lerna
• The pipelines, implemented as GitHub workflows, vary quite a lot

Here are (some of) the repos that we have studied:

• https://github.com/backstage/backstage
• https://github.com/RoadieHQ/roadie-backstage-plugins
• https://github.com/thefrontside/playhouse
• https://github.com/janus-idp/backstage-plugins

Approach

We will start with a simple solution and evolve it over time. The objectives of the first step are:

• stay on yarn 1 until it becomes the recommended version for Backstage (today, the documentation explains how to migrate to yarn 3, but the scaffolder still uses yarn 1)
• upgrade to the latest version of lerna
• use the independent mode for lerna, so that we can manage versions for our plugins independently
• implement a release pipeline that publishes plugins on npmjs.com