Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

Post reply on HN
Print view View original

221–230 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#221

Post by overfeed »

NewJazz wrote: post #195
noirscape wrote: post #14

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

Unfortunately I don't think there's really an answer to that conundrum that doesn't involve just spinning up your own git server and accepting all the operational overhead that comes with it. Hmm all that operational overhead... Of an ssh server? If you literally just want a place to push some code, then that really isn't that hard.

> ...that really isn't that hard.

Until the AI scrapers[1] come for you at 5k requests per second and you're doing operations in hard-mode.

1. Most forges have http pages for discoverability. I suppose one could hypothetically setup an ssh-only forge and statically generate a html site periodically, but this is already advanced ops for the average Github user

Re: Moving from GitHub to Codeberg, for lazy people

#222

Post by mememememememo »

jayd16 wrote: post #211
NewJazz wrote: post #195

Earlier quoted context omitted.

Unfortunately I don't think there's really an answer to that conundrum that doesn't involve just spinning up your own git server and accepting all the operational overhead that comes with it. Hmm all that operational overhead... Of an ssh server? If you literally just want a place to push some code, then that really isn't that hard.

Lots and lots of programmers have very little understanding and especially operation knowledge of how to host a public service. You can be an extreme graphics programmer and not know the web stack at all. And no, its not that hard once you learn. Except, now its a never ending chore when it was an appliance. Instead of a car you have a project car.

On the other hand you probably don't need to go full k8s and datadog on it. Just host it. Use a PaaS so you don't need to do Linux admin.

Re: Moving from GitHub to Codeberg, for lazy people

#223

Post by BeetleB »

AlienRobot wrote: post #204
noirscape wrote: post #14

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

To me that sounds like Github does too many things, not that Codeberg does too few.

Indeed. A code repository alternative should definitely not require an equivalent to Github Pages.

Re: Moving from GitHub to Codeberg, for lazy people

#224

Post by NewJazz »

mememememememo wrote: post #222
jayd16 wrote: post #211

Earlier quoted context omitted.

Lots and lots of programmers have very little understanding and especially operation knowledge of how to host a public service. You can be an extreme graphics programmer and not know the web stack at all. And no, its not that hard once you learn. Except, now its a never ending chore when it was an appliance. Instead of a car you have a project car.

On the other hand you probably don't need to go full k8s and datadog on it. Just host it. Use a PaaS so you don't need to do Linux admin.

I think both of you are misunderstanding what I proposed. You just need a single VM with an ssh server. Literally no web service needed, if all you want to do is host some code remotely.

Re: Moving from GitHub to Codeberg, for lazy people

#225

Post by NewJazz »

overfeed wrote: post #221
NewJazz wrote: post #195

Earlier quoted context omitted.

Unfortunately I don't think there's really an answer to that conundrum that doesn't involve just spinning up your own git server and accepting all the operational overhead that comes with it. Hmm all that operational overhead... Of an ssh server? If you literally just want a place to push some code, then that really isn't that hard.

> ...that really isn't that hard. Until the AI scrapers[1] come for you at 5k requests per second and you're doing operations in hard-mode. 1. Most forges have http pages for discoverability. I suppose one could hypothetically setup an ssh-only forge and statically generate a html site periodically, but this is already advanced ops for the average Github user

I wasn't proposing a full on forge, just a VM with a (key auth only) ssh server to push code to/from.

Re: Moving from GitHub to Codeberg, for lazy people

#226

Post by NewJazz »

tbayramov wrote: post #212
stephenr wrote: post #210

Earlier quoted context omitted.

Are you using an existing forge package (like eg Forgejo which codeberg is built on) or something custom?

Custom-built on top of libgit2.

Not trying to be dismissive/snarky... But why?

Re: Moving from GitHub to Codeberg, for lazy people

#227

Post by prmoustache »

mr_mitm wrote: post #67
prmoustache wrote: post #25

Earlier quoted context omitted.

The whole point of git is to be decentralized so there is no reason for you to not have your current version available even when a remote is offline.

How do people even on hacker news of all places conflate git with a code hosting platform all the time? Codeberg, GitHub or whatever are for tracking issues, running CI, hosting builds, and much more. The idea that you shouldn't need a code hosting platform because git is decentralized is so out of place that it is genuinely puzzling how often it pops up.

How do people on hacker news keep having reading issues?

The parent post mentionned: "the worst thing ever for me as a developer is having the urge to code and not being able to access my remote."

Emphasis one "code", not triaging issues, merging other people's branches, etc.

Besides there are tools to sync forgejo repositories including PRs and issues.

Re: Moving from GitHub to Codeberg, for lazy people

#228

Post by kbolino »

stephenr wrote: post #209
mejutoco wrote: post #198

Earlier quoted context omitted.

In case anybody is interested, having a bare git repo on a server is as easy as: # locally ssh git@example.com # server mkdir repo.git cd repo.git git --bare init # locally git remote add origin ssh://git@example.com/home/git/repo.git git push origin master P.S. I know it does not have the same features as github

If it's your ssh server and it's single user you don't need to use the "git@" part at all. Just store the repo and access it with your account. The whole git@ thing is because most "forge" software is built around a single dedicated user doing everything, rather than taking advantage of the OS users, permissions and acl system. For a single user it's pointless. For anyone who knows how to setup filesystem permissions…

There isn't much advantage that can be taken from O/S users and perms anyway, at least as far as git is concerned. When using a shared-filesystem repository over SSH (or NFS etc.), the actually usable access levels are: full, including the abilities to rewrite history, forge commits from other users, and corrupt/erase the repo; read-only; and none.

Re: Moving from GitHub to Codeberg, for lazy people

#230

Post by eddythompson80 »

NewJazz wrote: post #195
noirscape wrote: post #14

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

Unfortunately I don't think there's really an answer to that conundrum that doesn't involve just spinning up your own git server and accepting all the operational overhead that comes with it. Hmm all that operational overhead... Of an ssh server? If you literally just want a place to push some code, then that really isn't that hard.

Exactly, it's super easy. You only need the first part of this guide https://www.youtube.com/watch?v=40SnEd1RWUU
Post reply on HN