[FEATURE REQUEST] Allow git repos using ssh #1337

New Issue

GiteaMirror · 2026-03-22T17:21:58-05:00

GiteaMirror commented

2026-03-22 17:21:58 -05:00

Originally created by @ragchuck on GitHub (Aug 22, 2025).

I'm normally using SSH keys to authenticate against GitHub and my Forgejo instance.

It would be great if Komodo would also support that.

Originally created by @ragchuck on GitHub (Aug 22, 2025). I'm normally using SSH keys to authenticate against GitHub and my Forgejo instance. It would be great if Komodo would also support that.

GiteaMirror added the enhancement label 2026-03-22 17:21:58 -05:00

GiteaMirror commented

2026-03-22 17:22:01 -05:00

@MP-Tool commented on GitHub (Aug 22, 2025):

Hi! Thanks for your suggestion.
Just out of curiosity: is there a particular reason why you prefer using SSH keys over personal access tokens for authentication?
Tokens are generally considered more secure because you can configure their permissions in a very granular way and revoke them easily if needed.
Here’s a link to the official GitHub documentation about personal access tokens and how to manage their scopes:
https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token

Would love to hear about your use case!

@MP-Tool commented on GitHub (Aug 22, 2025): Hi! Thanks for your suggestion. Just out of curiosity: is there a particular reason why you prefer using SSH keys over personal access tokens for authentication? Tokens are generally considered more secure because you can configure their permissions in a very granular way and revoke them easily if needed. Here’s a link to the official GitHub documentation about personal access tokens and how to manage their scopes: https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token Would love to hear about your use case!

GiteaMirror commented

2026-03-22 17:22:03 -05:00

@ragchuck commented on GitHub (Aug 23, 2025):

Maybe it's personal preference, I feel like SSH-Keys are more convenient. I don't have to put them in the origin URL, they just work out of the box by lying in my ~/.ssh directory and I don't have to think about them anymore.
True, PAT can be revoked and are fine granular. But I also feel that SSH keys are one of the most secure things that you can get.

In my use case I currently have a VPS where I work with my user and I have another komodo user setup (using the systemd approach). As of now I work directly on the stacks compose files and env files and I also want komodo to manage the same stacks.
(I'm still having issues with permissions, though...)

Now, we're both working on the same repos on the machine. While I use my ssh key, I want komodo's use their ssh key, using the same origin URL. I'm not 100% sure if that works, but think it should, since both individual users have their own SSH keys.
You could even use a deploy key.

Does this makes sense?

@ragchuck commented on GitHub (Aug 23, 2025): Maybe it's personal preference, I feel like SSH-Keys are more convenient. I don't have to put them in the origin URL, they just work out of the box by lying in my ~/.ssh directory and I don't have to think about them anymore. True, PAT can be revoked and are fine granular. But I also feel that SSH keys are one of the most secure things that you can get. In my use case I currently have a VPS where I work with my user and I have another komodo user setup (using the systemd approach). As of now I work directly on the stacks compose files and env files and I also want komodo to manage the same stacks. (I'm still having issues with permissions, though...) Now, we're both working on the same repos on the machine. While I use my ssh key, I want komodo's use their ssh key, using the same origin URL. I'm not 100% sure if that works, but think it should, since both individual users have their own SSH keys. You could even use a [deploy key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#deploy-keys). Does this makes sense?

GiteaMirror referenced this issue

2026-04-11 10:43:09 -05:00

[PR #1337] Add support to generate resource json schema #3022

GiteaMirror referenced this issue

2026-04-13 15:21:00 -05:00

[PR #1337] Add support to generate resource json schema #4170

GiteaMirror referenced this issue

2026-04-19 14:13:26 -05:00

[PR #1337] Add support to generate resource json schema #4592

GiteaMirror referenced this issue

2026-04-22 00:51:09 -05:00

[PR #1337] Add support to generate resource json schema #5762