generated from importantimport/urara
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
36 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| --- | ||
| title: 'Platform Engineering: Building a portal for Developers with Backstage' | ||
| image: '/2024/backstage-medium-post/backstage-laptop-banner.webp' | ||
| # flags: | ||
| # - unlisted | ||
| summary: My Medium Post about Backstage.io | ||
| created: 2024-05-17 | ||
| # updated: 2022-10-20 | ||
| tags: ['TypeScript', 'Web', 'DevOps'] | ||
| --- | ||
|
|
||
| ## Check out my article on Backstage | ||
|
|
||
| I wrote an [article](https://medium.com/elca-it/platform-engineering-building-a-portal-for-developers-with-backstage-c51e74662eba) about the adoption of [Backstage](https://backstage.io/) as a central hub for developers in my company. My team and I oversee 600 projects with assets on both public cloud and on-premises, including Jenkins controllers and Azure subscriptions. | ||
|
|
||
| In this [Medium post](https://medium.com/elca-it/platform-engineering-building-a-portal-for-developers-with-backstage-c51e74662eba), I present how Backstage serves as an Internal Developer Platform (IDP), streamlining the management of these diverse resources and providing self-service capabilities for software engineering Teams in [ELCA](https://www.elca.ch/en) company. | ||
|
|
||
| I worked the last few months on integrating and developing custom plugins for self-service tooling and asset management. The stack of a Backstage plugin is quite standard: | ||
|
|
||
| - Backstage is a monorepo structure with plugins in separate folders. | ||
| - In the frontend, we use React. | ||
| - The backend uses NodeJS and Express for APIs. | ||
|
|
||
| Now, this Backstage instance is in production and also used by developers to deploy and manage their resources | ||
|
|
||
| For more information, please consult the article on Medium 😉 | ||
|
|
||
| <div class="alert shadow-inner"> | ||
| <div> | ||
| <span class="text-lg i-simple-icons-github !w-5 !h-5"></span> | ||
| <div> | ||
| <a href="https://medium.com/elca-it/platform-engineering-building-a-portal-for-developers-with-backstage-c51e74662eba"><h3 class="font-bold my-0">Medium Post</h3></a> | ||
| <div class="text-xs">Platform Engineering: Building a portal for Developers with Backstage</div> | ||
| </div> | ||
| </div> | ||
| </div> |
Binary file not shown.