Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

321–330 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#321
post #281

Earlier quoted context omitted.

I don't understand the hype around CI and that it's supposedly impossible to run something like that without Git, let alone Github. Like sure, a nice interface is fine, but I can do with a simpler one. I don't need a million features, because what is CI (in practice today, not in theory)? It's just a set of commands that run on a remote machine and then the output of those commands is displayed in the browser and it…

I find CI very valuable even on my solo projects. > what is CI (in practice today, not in theory)? It's just a set of commands that run on a remote machine and then the output of those commands is displayed in the browser and it also influences what other commands may or may not run. What exactly is the big deal here? The key is hermetically/reproducibly - you don't want to run commands on some random machine, you wa…

For a solo dev, what are the advantages of _not_ building on your own machine?

Is the compiling and test running too resource intensive?

Do you build every commit? If so, why?

I see the value in larger teams, but for solo stuff I just find it slow and annoying. I'm using go, and it compiles fast, so that could be a part of it.

Re: Moving from GitHub to Codeberg, for lazy people

#322
The main reason I use GitHub is because of the network effect. Most people have already a GitHub account and can easily open PR, issues, discussions.

So I'll wait until some big projects do it. For example, the day the Rust project moves away from GitHub I'll seriously consider. (Because I use Rust)

Re: Moving from GitHub to Codeberg, for lazy people

#323
post #281

Earlier quoted context omitted.

I find CI very valuable even on my solo projects. > what is CI (in practice today, not in theory)? It's just a set of commands that run on a remote machine and then the output of those commands is displayed in the browser and it also influences what other commands may or may not run. What exactly is the big deal here? The key is hermetically/reproducibly - you don't want to run commands on some random machine, you wa…

For a solo dev, what are the advantages of _not_ building on your own machine? Is the compiling and test running too resource intensive? Do you build every commit? If so, why? I see the value in larger teams, but for solo stuff I just find it slow and annoying. I'm using go, and it compiles fast, so that could be a part of it.

> For a solo dev, what are the advantages of _not_ building on your own machine?

I end up with all kinds of random crap on my own machine. It's very easy to accidentally e.g. globally install a library that wasn't properly listed in my dependency management. So having a separate standardised/controlled build environment is a good way to catch those. It also helps with flaky tests or random "works on my machine" problems - this way my tests are at least getting run on two quite different machines (different OS/arch/etc.)

Re: Moving from GitHub to Codeberg, for lazy people

#324
post #156

Earlier quoted context omitted.

Not to contradict you, but there's another important aspect to 'community' besides the bad contributors and the entitled complainers. That's discoverability. How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Searching each one individually is not a viable proposition. The search often ends on the biggest platform - Github. I'm not trying defend github here. The l…

That was solved by forums, tech mailing lists,... If you were interested in something, you hang around the communities and almost everything that was interesting enough will pass by.

Do you hang around every forum or mailing list that discusses the solutions to problems that you may potentially encounter in the future? The type of problem I'm talking about isn't one that can be foreseen years in advance.

Re: Moving from GitHub to Codeberg, for lazy people

#325
post #156

Earlier quoted context omitted.

Not to contradict you, but there's another important aspect to 'community' besides the bad contributors and the entitled complainers. That's discoverability. How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Searching each one individually is not a viable proposition. The search often ends on the biggest platform - Github. I'm not trying defend github here. The l…

> How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Word of mouth. Package managers. Search engines. Your LLM of choice. Does anyone seriously use GitHub search to discover new projects?

Word of mouth: What if it's just some random script a guy created in a weekend? I have my code used by others in such a manner.

Package managers: Same problem as above. You missed the point of free software.

Search engines: They do a disastrous job of indexing anything on a forge. You might as well yell at the clouds instead.

LLM of choice: I'm not taking this seriously.

> Does anyone seriously use GitHub search to discover new projects?

I don't even understand the point of such questions. None of the solutions you proposed are any better solving what I described than the insufficient method I wrote about.

Re: Moving from GitHub to Codeberg, for lazy people

#326
post #156

Earlier quoted context omitted.

Not to contradict you, but there's another important aspect to 'community' besides the bad contributors and the entitled complainers. That's discoverability. How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Searching each one individually is not a viable proposition. The search often ends on the biggest platform - Github. I'm not trying defend github here. The l…

Ideally this should be something search engines handle - but they do a poor job in specialised areas like code repos. It's helpful to have a github mirror of your "real" repo (or even just a stub pointing to the real repo if you object to github strongly enough that mirroring there is objectionable to you). One day maybe there will be an aggregator that indexes repos hosted anywhere. But in many ways that will be bac…

> The Fediverse seems to dislike global search. Or is that just a mastodon thing?

Lemmy seems to do a decent enough job at global searches. It's most likely just a mastodon problem.

Re: Moving from GitHub to Codeberg, for lazy people

#327
post #132

Earlier quoted context omitted.

> and use robots.txt as a guide of what to crawl rather than what not to crawl Mental note, make sure my robots.txt files contain a few references to slowly returning pages full of almost nonsense that link back to each other endlessly… Not complete nonsense, that would be reasonably easy to detect and ignore. Perhaps repeats of your other content with every 5th word swapped with a random one from elsewhere in the co…

So, basically iocaine ( https://iocaine.madhouse-project.org/ ). It has indeed been very useful to get the AI scraper load on a server I maintain down to a reasonable level, even with its not so strict default configuration.

Yes, except with the content being based on the real content rather than completely random. My intuition says that this will be more effective, specifically poisoning the model wrt tokens relating to that content rather than just increasing the overall noise level a bit (the damage there being smoothed out over the wider model).

Re: Moving from GitHub to Codeberg, for lazy people

#328
post #288

Earlier quoted context omitted.

I didn't misunderstand. Sshd is a web service. Most folks don't already know how and don't want to set up a machine that is always on, that will restart on power loss, that will have a static IP or dynDNS, with a domain name and proper routing and open ports and certs and enough bandwidth and that's before you even worry about actual security and not just what is needed to work.... It's actually a big annoyance if yo…

ssh isn't a web service (some would argue that smtp and ftp aren't too as they came before the web). And I believe GP was talking about the only thing you need is: ssh user@remotehost git init --bare repo.git And then you can add the remote to your local repo with git remote add origin user@remotehost:repo.git Now all you need to do is git push origin branch_name Replace origin with another identifier if it's already…

The rest of the owl: go to provider, set up VM (20 questions) log into root. SSH for login. set up firewalls. create non-root user. useradd or adduser? depends if you want a home dir I guess. debug why you can't ssh in. Finally get in. sudo apt update. sudo apt install git (or is it named something else?). install failtoban. install fw.

then do above.

then troubleshoot.

set vm backup policy.

save myriad passwords and secret to bitwarden.

get ubuntu to stay up to date.

Re: Moving from GitHub to Codeberg, for lazy people

#330
post #280
post #192

Earlier quoted context omitted.

Finding an HTTP+FTP server was easier than finding github. Your OS probably has a FTP client installed already, but finding another one is easier than finding and most definitely easier than learning git. And if you already knew how to write/make HTML you'd for sure already know all of that too.

> Finding an HTTP+FTP server was easier than finding github. No it wasn't. Seriously, where?

Didn’t your ISP provide you with free FTP storage? The French ones did, at least.
Post reply on HN