Building a Fully Operational Internal Developer Platform

Internal developer portals sit on top of platforms, made of underlying resources and platform assets, from reusable workflows to kubernetes and GitHub. In this live coding session we will build an internal developer portal from scratch. We will define blueprints and relations, which will essentially create a data model for the software catalog, and create the underlying developer self-service infrastructure.
Subscribe the channel:‪@getport‬
#developerportal #Infra #Kubernetes
▬▬▬▬🚢In this session you will learn🚢▬▬▬▬
➡How to define the data model for the internal developer portal
➡How to use the Kubernetes and GitHub exporters
➡How to create scorecards and calculate metrics
➡How to create dashboards and reports
▬▬▬▬▬▬▬📱Contact us📱▬▬▬▬▬▬▬▬
Via Slack ➡ join.slack.com...
Via LinkedIn ➡ / getport
Via Github ➡ github.com/por...
Try Port now ➡ www.getport.io...
The source code used in this session can be found on GitHub: github.com/por...

[@andrewnhien9714]

amazing video. Hope release more live code video!

[@felixh454]

thank you for the live demo. i really like port so far and especially the ease of use in comparison to backstage from my playing around with both of them. just a quick question: is there an ETA on when the port operator for local deployments will be out?

[@getport]

Hi Felix! We're working on a version of Port that can be used in the customer's cloud. to apply for the beta write to us at [e-mail] :)

[@powerademonke]

Can port be used to also create internal client side apps within IDP? i.e if we wanted to build some react app that needs to manipulate some db data.

[@getport]

Hi there! While Port does not allow you to develop applications directly inside the IDP, there are are a few different approaches Port provides: 1. Self service actions - Actions like scaffold can help you develop applications. 2. Aggregations and calculations - Port allows you to analyze and perform calculations + aggregation on the data that is inside Port. Port leverages the fact that you ingest the data into the catalog, allowing you to do more operations on the centralized data catalog. If you want to talk more, feel free to email our team at [e-mail] :)

[@andrewnhien9714]

what do you need to get enough information to get the complete graph like at 49:15? git access, k8s access, or info from the system's json that you import? can you share the json system file?

[@getport]

The data you see in the graph is made up mostly from K8s and Git resources ingested to Port and tied together using relations inside the catalog. You can view all of the JSONs used in this webinar, as well as a step-by-step guide to setup a similar portal in our public GitHub repo for this webinar, you can find it on github - github.com/port-labs/e2e-idp-webinar-may-23

[@andrewnhien9714]

@@getport Thank you for the work you are doing. I've enjoyed my experience with Port, but there's one point I'd like to ask you. If the company has many products, enviroment for individual team, how will it be organized in Port, about Service, monitor, Jira, system... Can you make a video or share your experience on that?

[@getport]

Hi @@andrewnhien9714 ! Port is made by design to be extensible and support any use case, architecture, and infrastructure layout you want to model. As such, it is easy (and also recommended) to ingest data from and integrate Port with a plethora of systems. After you have the data in place, you can use the UI interface to create custom views with the different filters and groupings that make sense for you the consumers in your organization. We have plans to post a webinar around the topic of custom integrations and managing data layouts in Port, so I suggest checking it out when it is released!