docker-caddy-go-api VS meshery

This article isn't about any of the technologies involved. I'm trying to revisit my roots and write a comprehensive tutorial on the project. There is a work-in-progress version as well as the repository at Github. No, here I'm going to assume the reader is familiar with Go, SPAs, Caddy and Docker, and is looking for a method to tied them all together in a localhost environment. Non-standard ports are used to avoid competing with other web services. These steps have been tested on Windows but should be adaptable to other operating systems.

Meshery is an open-source cloud infrastructure and Kubernetes management platform that provides a unified interface for simplifying the deployment, management, and observability of cloud-native applications. It acts as a central control plane for managing Kubernetes clusters, containerized applications, and associated resources.

After searching through many different open source repositories, I was unable to find anything that peaked my interest. I was struggling and was slowly loosing hope. However, one thing that kept on occurring was my ongoing PR fixes for my release 0.3 external project Meshery. My ongoing PR was full of reviews, and I was constantly making small changes based off those comments. That is when it sparked to me that this pull request was essentially what our professor was looking for in release 0.4, so I decided to do two things.

Most Open-Source projects have a contributing doc(usually a CONTRIBUTING.md file at the root of the repo) that contains all the necessary details on how to set up your development environment, coding conventions you have to follow and much more.

My first issue was This which was regarding the improper margins on the management page, a component/ui and framework/react issue :) Tbh, it wasn't a huge amount of work, I just had to fix the padding values of the component as shown below and I was good to go