gatus VS leapp

Kuma Vs. Gatus

Mostly working on devops tasks. Researching solutions for status page for explorer and other services. Found https://github.com/TwiN/gatus but it not cover all needed cases. Researching grafana now.

Gatus is a health dashboard that gives you the ability to monitor your services using HTTP, ICMP, TCP, and even DNS queries as well as evaluate the result of said queries by using a list of conditions on values like the status code, the response time, the certificate expiration, the body and many others.

I also recently started working on a SaaS for a managed solution of Gatus: https://gatus.io

You can have a look at Gatus but I don't know how it will handle that many hosts (I have maybe 30). It has an API but it's read only, however the config file is monitored so you could probably write a script to dynamically add and remove hosts.

I create a health status page in Go nearly a year ago.

I'm also making a SaaS out of it, though it's still a work in progress: gatus.io

Another alternative I found here on HackerNews in another "Uptime Robot Alternatives Thread" and which I use in my home setup is https://github.com/TwiN/gatus . Very easy setup and configuration.

But fear not! This article will show you how you can improve your CDK templates by making wise use of our open-source tool.

Leapp is my go-to tool for accessing my cloud accounts. I was fed up with manually managing local development and operations credentials, so I automated everything most securely. I can’t count how much time it saved me over the years.

Generally, using IAM users is not the best practice. Instead, it's far better (and more common) to use SSO and grant access through IAM roles. Furthermore, it's even safer (and more convenient) to use tools like Leapp or aws-vault to manage AWS access.

If you are a developer and need to access programmatically, you can use Leapp to access with MFA.

At the moment I'm struggling with my founder role and accountabilities inside the project.

I've switched from a DevOps position to become the Product Owner, managing the delivery of the open-source project and the day to day work, but now I see lack of time in developing a real evangelism and DevRel things inside the Leapp project.

I'm completely aware that this is THE crucial part of an open-source project and I really love OSS because of the contributing from all around the world.

But is turning that maintain and grow a community around the project, make the project well known, is a full time job for a founder of a project.

I still don't know if I have the right skill for that kind of job and where a such particular job can bring me in the future, together with the Noovolari company.

BTW, this is my project (https://github.com/Noovolari/leapp) and I would love to chat more with you!

Solid point, but not everyone will notice it without someone telling you that the project even exist.

the experience with my project (https://github.com/Noovolari/leapp) is that if someone know the project it become an habit.

Thanks for the additional context, helps to understand your situation and resources.

> BTW, this is my project (https://github.com/Noovolari/leapp)

Looks great. A few suggestions for the first impression opening the project:

- Switch to dark mode and verify that the images work in the README and other docs. There is a logo which cannot be seen on the site, it's dark and black.

- Focus on telling the "problem to solve" and "why" in the introduction https://github.com/Noovolari/leapp#leapp I initially did not understand the term "cloud access app"

- The screenshot description is AWS focussed. https://user-images.githubusercontent.com/9497292/114399348-... If you don't know AWS specifics, it is hard to understand. Think of a more high level catchy architecture overview, or working example. Catch your marketing term with "multiple cloud access strategies". Maybe use a Gif to showcase the key items as done in the one in "key features"

- Installation links to a release download page. https://www.leapp.cloud/releases Improve this, highly recommend to create documentation guides for Windows, Linux and macOS, explaining the different commands step-by-step, more tutorial alike.

Actually, your website has a docs section, but it is not linked from the GH Readme. Suggest to link to https://docs.leapp.cloud/installation/install-leapp/ instead of the releases page.

Here's a PR to fix it: https://github.com/Noovolari/leapp/pull/215

- You are using MkDocs for the documentation. That's amazing <3

- PR template - while fixing the readme, I was confused by the template structure. Maybe get inspired by GitLab MR (similar to PR) templates? Gary Bell wrote a great blog post about them: https://www.garybell.co.uk/merge-request-templates/

- You are using a DCO which requires all commits to be signed off. That's impossible with using the browser to make direct edits to the docs, or otherwise suggestions. It may throw off contributors after their first pull request (it throws me off every time I consider contributing on a mobile device).

Did now on my desktop terminal:

cd /tmp && git clone https://github.com/dnsmichi/leapp && cd leapp && git checkout patch-1 && git commit --amend -s && git push -f

Suggestion: Document the DCO requirement more visible, e.g. with a badge in the README.

- The PR fails because because of a check https://github.com/Noovolari/leapp/runs/4971776167?check_sui...

"Error: No release type found in pull request title "Update URLs to installation docs in README". Add a prefix to indicate what kind of release this pull request corresponds to (see https://www.conventionalcommits.org/)."

That's additional work for contributors. After fixing the DCO sign-off, the next thing to do. Then again, the commit also needs a "docs: " prefix. At this point, I would have lost the desire to contribute.

- Why is the contributing.md hidden in the .github directory (https://github.com/Noovolari/leapp/blob/master/.github/CONTR...) and not present in the main repository? I was specifically looking for it at the repository top level when looking to contribute.

- https://github.com/Noovolari/leapp/blob/master/.github/CONTR... encourages you with "Please send a GitHub Pull Request to Leapp with a clear list of what you've done (read more about pull requests)."

What's a clear list of changes?

Suggestions in a new PR: https://github.com/Noovolari/leapp/pull/216

- https://docs.leapp.cloud/contributing/get-involved/ links from the docs to contributing.md As discovered above, contributing.md is more a "things to review" document. It should be the call-to-action document. Or maybe move the content from contributing.md entirely into your documentation - and only link there. I do the same with https://o11y.love/contributing/ for example

- Make it easy to spin up a development environment - I don't see any guides to do so?

Suggestion: Add Gitpod or a local Docker build and a development.md to your repository. This will be critical for your success to attract contributors.

- https://docs.leapp.cloud/contributing/project-structure/ exists but is not linked in contributing.md

- Labels help wanted / good first issue are used, but they are not explained/linked in the contributing guide. If you are not familiar with these label types, contributions are harder.

Suggestion: Fix this by adding the Call-to-action in your contribution guides.

https://github.com/Noovolari/leapp/issues?q=is%3Aissue+is%3A... + https://github.com/Noovolari/leapp/issues?q=is%3Aissue+is%3A...

Above are my first impressions starting with the project and trying to find ways to contribute. I did not read the source code yet. I'd suggest addressing them, and then focus on DevRel and marketing ideas. The first impression of a project is crucial to help seed the community plants :)

Use Leapp to manage and secure your CLI credentials from a secure point of view