profile VS debug-toolkit

So, have your GitHub registration properly filled out. That way you don't need to make any code changes. 🤖

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

That account has the "Make profile private and hide activity" option turned on in https://github.com/settings/profile which hides your contributions, activity, followers, followings, stars, etc.

Abra o GitHub, e vá para Settings,

Go to your settings at https://github.com/settings/profile and check "Include private contributions on my profile"

By opting to allow developers to use their own accounts to sign in, with or without SAML SSO, developers are able to stay in control of their own GitHub identity. They also don’t have to manage a separate “work” GitHub account and can keep data such as commit statistics all in one place. To see it in action, go to https://github.com/settings/profile and enable the checkbox as seen in the screenshot below:

So, have your GitHub registration properly filled out. That way you don't need to make any code changes. 🤖

I just get 500 on the homepage, and my profile also 500s when logged out. Most other things still seem to work, including https://github.com/settings/profile where I could turn it off.

To create the GitHub Client ID and Client Secret, go to https://github.com/settings/profile, Developer Settings on the left-hand nav-bar, OAuth Apps, New OAuth App. Fill in a name and your localhost with port for the homepage URL. Copy the homepage URL and add /api/auth/callback/github. This will allow the /api/auth/[...nextauth].ts file to catch this callback URL and use it to create a user in the database. The form should look something like this:

We're very much not a company of one anymore, but I used Unicorn Platform for our startups website (http://robusta.dev)

It's optimized for building a decent looking startup website in half an hour.

We now have an in house designer and frontend team so the whole thing will be replaced soon... But it got us fairly far.

I use it all the time when hiring!

We're open source (https://robusta.dev) and very involved in the kubernetes ecosystem so GitHub history is extremely relevant when we look at candidates.

We'll hire people with no GitHub activity too, but when it's available it's great

Github: https://github.com/robusta-dev/robusta Marketing site: http://robusta.dev/ Docs: https://docs.robusta.dev/master/

We're using Hikaru extensively in Robusta. The best part (well, other then the ease of use) is that Tom is super responsive to issues on GitHub and always happy to help.

To everyone saying that Kubernetes is unnecessary, try implementing autoscaling, service discovery, secrets management, and autohealing in a vendor independent way without it.

Of course none of that is necessary for a self hosted home lab, but neither is gitops.

This is a very nice example of how to set stuff up properly.

OP, I would love to see Robusta (https://robusta.dev) as part of this too. It's definitely in line with your vision of automating everything, as it let's you automate the response to alerts and other events in your cluster. (Disclaimer: I'm one of the maintainers)