Hi, y’all! This week’s newsletter highlights contributions to simplifying setting up documentation for monorepos and to configure multiple SonarQube instances. We also share a 20% discount on KubeCon on-site tickets.
As pointed out by dariocurr, when you’re setting up documentation for a monorepo, you may end up having to do redundant work declaring
nav for every subdirectoy.
Borrowing the author’s example, let’s say you have the following in your general
Thanks to dariocurr, you can now leave docs_dir and nav blank on each subdirectory, so it picks up the parent’s config, as in the example below. Before you had to re-specify these properties in every file.
The feature will be available in a release soon, check out the PR in the meantime.
If you’re working with monorepos, be sure to check out Roadie’s guide to modeling monorepos in Backstage.
Neemys championed the initiative of allowing different SonarQube instances to be specified for different services. This feature was originally requested in a context where the services belonged to several clients and thus used their own SonarQube instance.
If you already use the SonarQube plugin, check out the new release as there might be breaking changes that affect you: the backend was extracted to a separate plugin
We’re thrilled for the first ever BackstageCon, taking place within KubeCon North America in Detroit. To attend, you must have a KubeCon ticket. Roadie is sponsoring the event, so we can help you shave 20% off of the KubeCon’s on-site ticket with this code: [email protected]
We hope to see you all there!
Before saying good bye, I want to welcome AppFolio to the community as the most recent adopter!
Talk to you next week!