this post was submitted on 18 Aug 2025
137 points (97.9% liked)

Opensource

4771 readers
158 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient

⠀

founded 2 years ago
MODERATORS
pylapp@programming.dev
137
Pixelfed, Instagram alternative, move to Codeberg (codeberg.org)
submitted 4 months ago by cm0002@piefed.world to c/opensource@programming.dev
21 comments fedilink hide all child comments
top 21 comments
sorted by: hot top controversial new old
[–] jeena@piefed.jeena.net 16 points 4 months ago (3 children)

So yesterday I set up forgejo, which is the software behind codeberg, and imported all my 88 git repos from github, so far so good.

But then I spent the rest of the day trying to figure out how to be able to use port 22, which I already use for sshd to share it with forgejo so I could clone and push to it without the need of a non standart Port and I am almost giving up on it, almost. I will try today again, but I'm running out of options and the documentation is not telling me how to set it up.

Any tips are welcome!

[–] LodeMike@lemmy.today 6 points 4 months ago

You have to

  1. Make sure access is allowed on the sshd server side for the user Forgejo is running on
  2. Ensure it's enabled in Forgejo settings
  3. Add your SSH key into your user settings
[–] GammaGames@beehaw.org 5 points 4 months ago* (last edited 4 months ago) (1 children)

Odd, setting this up with gitea (which forgejo was forked from) was painless, maybe their guide will help. There is a few different options

[–] jeena@piefed.jeena.net 8 points 4 months ago (1 children)

So interesting, actually yesterday I was sporadically reading that page but not following it exactly. Now that you posted the link I really paid attention and followed it again, and I have the feeling I did exactly the same steps, but now it just worked!

Thanks so much, this is awesome, now I really don't need GitHub anymore.

Here is the script I used to migrate: https://git.jeena.net/jeena/github2forgejo

[–] GammaGames@beehaw.org 4 points 4 months ago

I’m glad it helped! From what I remember when I checked out forgejo their documentation was really lacking, but some of it has gotten better since they did the hard fork

[–] poVoq@slrpnk.net 3 points 4 months ago (2 children)

Why the need to push via ssh? I am genuinely wondering, since you can easily push without having that enabled at all.

[–] Mihies@programming.dev 6 points 4 months ago (1 children)

That's an odd question as ssh is very convenient and secure compared to https.

[–] poVoq@slrpnk.net 1 points 4 months ago (1 children)

Convenient, yes. But if used like that quite insecure.

[–] Mihies@programming.dev 3 points 4 months ago

Oh, no. It's more secure than https if done properly (i.e. backed by hardware key and/or a quality password) I'd say.

[–] jeena@piefed.jeena.net 5 points 4 months ago (1 children)

Because otherwise I will need to set up a different way of logging in to authenticate on every computer. I'm using ssh for every git server. How do you authenticate, with a different access token for each git server in ~/.gitconfig?

[–] poVoq@slrpnk.net 0 points 4 months ago (2 children)

Ok, I understand that this is a bit inconvenient, but you can use a password manager for the required git push logins.

But you are not concerened that someone compromising your ssh keys gets full access to all your repos?

[–] jeena@piefed.jeena.net 3 points 4 months ago (1 children)

How would they get my private key? I mean if they already have access to my private key on my computer then I have much bigger problems than them having access to the anyway public git repos.

Perhaps I'm misunderstanding the thread model you have, but isn't ssh the standard way of accessing git repos because it is so much more secure compared to a username and password?

[–] poVoq@slrpnk.net 0 points 4 months ago* (last edited 4 months ago)

They can impersonate you and push code into the repos in your name with a high likelyhood of you not noticing it.

The typical hobby dev machine isn't particularly secure and for sure less secure than the typical server. Accessing everything from there with a single key is a pretty gaping security hole IMHO.

There seems to be this common misconception that ssh keys are more secure than passwords, but that is only true when you use really weak passwords that you keep in your head instead of a password manager.

If you want to actually increase your security then you need to set up a second factor auth with a seperate device.

[–] tyler@programming.dev 1 points 4 months ago* (last edited 4 months ago) (1 children)

Huh? ssh is much more secure than https.

Edit: the security is essentially the same, but having one password every machine vs individual ssh keys seems like a huge advantage to me. Also ssh means you don’t ever accidentally allow read access that you don’t mean to.

[–] poVoq@slrpnk.net 1 points 4 months ago (1 children)

Well, the situation in this case seems to be the exact opposite, i.e. reusing the same SSH key for multiple repos Vs. being easily able to have different passwords for different repos with a password-manager.

[–] tyler@programming.dev 1 points 4 months ago (1 children)

How would you have different passwords for different repos?

[–] poVoq@slrpnk.net 1 points 4 months ago

On different forges, which is what OP was talking about.

[–] jeena@piefed.jeena.net 15 points 4 months ago

Hm, I think the title is wrong. If you check it then the last commit in codeberg was 3 years ago and the last commit on github is 4 days ago.

[–] artiman@piefed.social 7 points 4 months ago

The title is confusing and wrong can you fix it?

[–] mesamunefire@piefed.social 4 points 4 months ago

Great news!!