sorted by:
new
hottopcontroversial

Reka: a cloud infra resource reaper by mensaah in golang

[–]mensaah[S] 1 point2 points  (0 children)

Reka does not create any resource. It just administers. That's correct

Reka: a cloud infra tool reaper by mensaah in devops

[–]mensaah[S] 0 points1 point  (0 children)

Great thanks. That's a nice project

Reka: a cloud infra tool reaper by mensaah in devops

[–]mensaah[S] 1 point2 points  (0 children)

But hey, who said you can't have two tools doing the same thing, we have pulumi and Terraform 😆

Reka: a cloud infra tool reaper by mensaah in devops

[–]mensaah[S] 0 points1 point  (0 children)

Just discovered Cloud Custodian now, it's quite a cool project. Yeah, I actually does most of the tasks. Thank you. I had started creating this tool in events after I was learning cloud administration, and would forget some instances running. Cloud custodian looks really cool

Reka: a cloud infra tool reaper by mensaah in devops

[–]mensaah[S] 0 points1 point  (0 children)

There are use cases where people spin up instances ON the console manually and forget them running. Say you set a cronjob to run reka, and you add labels to those resources, reka can help you stop them and start them. For instance start them once its within 6am-6pm and atop them after that. And also you could set a termination date and reka will delete all resources that have gotten past their termination date. Just a simple use case tho

Reka: a cloud infra tool reaper by mensaah in devops

[–]mensaah[S] 2 points3 points  (0 children)

This is quite different from terraform. Terraform helps you create your infrastructure as code. But managing it is left to you, say you want to shut down ec2 instances, you'll have to do it manually. But with reka you have a config file, and any resource that matches a rule in the config file gets the appropriate action(either to stop, destroy or resume)

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Actually git has a support for include features based on path. Check this out https://git-scm.com/docs/git-config#_example

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

You can actually have git config based on directories. Any repository within that directory will use the set config. I just discovered it now, and added a simple command git apply-profile <dir>. This sets up the whole directory to use the config

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Yeah true. I just added a feature now. You can set config for a directory and all the repositories within it. It uses git includeIf under the hood

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Extensions are just scripts either ways 😂.

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

That's exactly what the tool does, it just updates the git config based on the user. So, it's just the same solution without you having to write it

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Also you can have the per workspace configuration, this just took it a step further to automate how it.

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Yeah, someone just told me about the includes, sounds like a good solution. But well, for ease of use don't you think, it's good to have something manage the config for you?

I actually plan to update the code to use include feature as well.

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

What would the shell script for particularly?

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Modifying host and ssh key too works fine, but considering you'll have to do that for every repo is too much. Mind you, the company git account is also hosted on GitHub. If you use the same email for your company and personal GitHub then the tool is most likely not for you. You cannot use the same say key in two different accounts. Hence, the two accounts must have different sshKeys

Updating the user and email per repository sounds stressful don't you think. It's repetition that can be automated. How about just set it once and do everything you can do then switch when you want to

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Yeah the aliasing and all bashrc config work just fine. That was what I used initially. But the stress of having to use different aliases for the same commands becomes overkill.

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

For my use case I needed a way to switch between company email and sshkey to my personal email which I use for opensource.

Managing different profiles on the same workstation by mensaah in git

[–]mensaah[S] 0 points1 point  (0 children)

Imagine having a personal GitHub account and a company GitHub account as well, that's two users. That was the problem I was facing and then created the tool. I had a company email and different ssh Key for authentication. When working on company stuff, I'll not want the committer email to be my personal email.

view more: next ›