validate-configs-action VS Logdy.dev

Took me bout 2 days for the initial release of the config-file-validator. I had been thinking about it for a while and was able just to knock it pretty quickly

https://github.com/Boeing/config-file-validator

Project Link: https://github.com/Boeing/config-file-validator

Github Action to use the config-file-validator (https://github.com/Boeing/config-file-validator) to recursively scan the directory structure of a repo for config files and validate their syntax as part of a CI/CD pipeline.

This is useful as a quick quality gate in your CI pipeline to validate that a syntax error was not introduced in the latest commit. Currently XML, JSON, YAML, INI, and TOML are supported with CSV, HCL, and Plist coming in the next release.

Here's how to add it to your existing workflow: https://github.com/kehoecj/validate-configs-action/tree/main...

For those who find this tool interesting, I can recommend to take a look at Logdy.dev (https://logdy.dev) https://github.com/logdyhq/logdy-core

I've built a first version of Logdy[1] over the weekend. Since then I have been developing it and it's getting traction and attention.

Logdy is a real-time logs browser that is meant to replace viewing logs in a terminal during development stage. I was tired of browsing and searching through infinite stream of non-searchable json whereas having such a great tool as DataDog on production. I've felt that development process lacks this kind of tool and decided to scratch my own itch.

[1] https://logdy.dev

You can forget about messy terminal filled with lines of logs. Meet Logdy.

Personally, I don't care about the build times as they happen in a GH workflow [1] and the compiled sources get updated to Cloudflare Pages that's how [2] gets deployed.

[1] https://github.com/logdyhq/homepage/blob/main/.github/workfl...

[2] https://logdy.dev

I have a pipedream.com workflow that does exactly that, in 5 lines of code, it catches whatever is in the POST body and sends an email to me. You can check it on https://logdy.dev

What added value your service provides, beside the fact I have to share email addresses I receive with you?

Congrats on the launch, nice project! I recently launched https://logdy.dev which attempts to address the problem but in a more wide space: any kind of process stdout -> web UI. You can run it with k8s (kubectl logs -f). I'm actually writing a blog post about it as we speak and will definitely mention kubetail as well. Ofc, your project addresses the problem more specifically, I just thought to mention Logdy in case somebody is looking for a swiss-knife solution for all kinds of logs.

Latest release: https://github.com/logdyhq/logdy-core/releases