4 ms·
Why a web page and not directly the git log? If style is necessary, reformat the log data with some fancy ASCII art?
by ykonstant 2y ago
Why a web page and not directly the git log? If style is necessary, reformat the log data with some fancy ASCII art?
- teqsun 2y agoI'm assuming the PO isn't technical so git-log, git-blame, etc. are over their head. Which itself begs why they'd need this level of detail on the codebase.
- chrsig 2y agothe "which ones are deployed where" bit is nice. if you're managing a lot of repos and deployments, yeah, that kind of thing can get really messy. i don't care how it's presented, via webpage or cli tool or whatever -- just saying that when you are working at larger scale, those are very reasonable things to want to see in one spot at a glance. the need dissipates as you scale down.
- stackskipton 2y agoSure, but that's best handled by Application reporting it via monitoring system. For example, at my company, we embed git commit, version and branch that last merge to main in container environment variables. Prometheus then exposes that as labels so we can just look any time it comes up. If we wanted to build a Grafana dashboard, that could be done easily as well. I'm sure most monitoring systems have some way to loading that into their system.
- chrsig 2y agoSure, and the commenter's PO didn't specify how to get him a webpage. All very reasonable, see?
- marcosdumay 2y agoIt's hard to put your current ops configuration inside the git log. If you found some way to do that that fits well in the philosophy of a stream of immutable changes, I'm interested in reading your ideas.
- andiveloper 2y agoWe are using git tags on the commit to figure out what is currently deployed where, e.g. "dev-stage", "test-stage" etc.