Migrating Dillo from GitHub • Hacker News Board

Re: Migrating Dillo from GitHub

#111

Post by Etheryte » Sun, Nov 30, 2025, 7:13 PM UTC

IgorPartola wrote: post #99

xrd wrote: post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

What exactly is the advantage of running something like GitLab vs what I do which is just a server with SSH and a file system? To create a new repo I do: ssh example.com ‘mkdir repos/my-proj.git && cd repos/my-proj.git && git init —bare .’ Then I just set my remote origin URL to example.com:repos/my-proj.git The filesystem on example.com is backed up daily. Since I do not need to send myself pull requests for persona…

This is kind of like asking what the point of Dropbox is when we have rsync. Rsync is nice, but most people won't know how to use it.

Re: Migrating Dillo from GitHub

#112

Post by jbaber » Sun, Nov 30, 2025, 7:14 PM UTC

mystifyingpoi wrote: post #68

ramon156 wrote: post #65

> To avoid this problem, I created my own bug tracker software, buggy, which is a very simple C tool that parses plain Markdown files and creates a single HTML page for each bug. I love this. I used to be a big fan of linear (because the alternatives were dog water), but this also opened the question "why even have a seperate, disconnected tool?" Most of my personal projects have a TODO.md somewhere with a list of th…

> As it is simply plain text Well, if your bugs can be specified clearly in plain text and plain text only, then yeah, I'd also advocate for this approach. Unfortunately, that's not really the case in any bigger software project. I need screenshots, video recordings that are 100 megs, cross-issue linking etc. I hate JIRA (of course) but it gets it right.

We can enter e-mail's h*ll and just have attachments be base64 blobs.

Re: Migrating Dillo from GitHub

#113

Post by throwfaraway135 » Sun, Nov 30, 2025, 7:14 PM UTC

Although I'm not a fan of GH, I appreciate the ability to see how popular/valid some project is by looking at the number of stars (I know this is far from a perfect signal). I'm much less likely to try projects that have a low number of stars, or projects in different places.

Re: Migrating Dillo from GitHub

#114

Post by WD-42 » Sun, Nov 30, 2025, 7:14 PM UTC

gchamonlive wrote: post #49

xrd wrote: post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

https://forgejo.org/docs/latest/user/actions/basic-concepts/ It's a shame that GitHub won the CI race by sheer force of popularity and it propagates its questionable design decisions. I wish more VCS platforms would base their CI systems on Gitlab, which is much much better than GitHub actions.

Both are yaml jungles, I hate them equally.

Re: Migrating Dillo from GitHub

#115

Post by emfrosztovis » Sun, Nov 30, 2025, 7:26 PM UTC

0x696C6961 wrote: post #47

> On the usability side, the platform has become more and more slow over time The best reason right here.

Off-topic, but as a non-native speaker I’m curious if it’s common to say “more and more slow” as opposed to “slower and slower” (maybe to emphasize the adjective?)

Re: Migrating Dillo from GitHub

#116

Post by xrd » Sun, Nov 30, 2025, 7:26 PM UTC

iamkonstantin wrote: post #66

adamcharnock wrote: post #28

Earlier quoted context omitted.

We've been looking at Forgejo too. Do you have any experience with Forgejo Actions you can share? That is one thing we are looking at with a little trepidation.

We use them in our shop. It's quite straightforward if you're already familiar with Github Actions. The Forgejo runner is tiny and you can build it even on unsupported platforms ( https://code.forgejo.org/forgejo/runner ) e.g. we've setup our CI to also run on Macs (by https://www.oakhost.net ) for App Store related builds. It's really quite a joy :)

Are you building MacOS apps? More specifically, are you doing code signing and notarization and stamping within CI? If so, is this written up somewhere? I really struggled with getting that working on GitLab. I did have it working, but was always searching for alternatives.

Re: Migrating Dillo from GitHub

#117

Post by simpaticoder » Sun, Nov 30, 2025, 7:27 PM UTC

oooyay wrote: post #102

IgorPartola wrote: post #99

Earlier quoted context omitted.

What exactly is the advantage of running something like GitLab vs what I do which is just a server with SSH and a file system? To create a new repo I do: ssh example.com ‘mkdir repos/my-proj.git && cd repos/my-proj.git && git init —bare .’ Then I just set my remote origin URL to example.com:repos/my-proj.git The filesystem on example.com is backed up daily. Since I do not need to send myself pull requests for persona…

Collaboration and specifically collaboration with non git nerds. That's primarily what made GitHub win the VCS wars back in the day. The pull request model appealed to anyone who didn't want to learn crafting and emailing patches.

Yes, it's the PRs, and there is a misunderstanding I think because the OP and the GP's use-cases are quite different. Self-hosting your own repository on a remote server (and perhaps sharing it with 1 or 2 collaborators) is simple but quite different than running a public open source project that solicits contributions.

Re: Migrating Dillo from GitHub

#118

Post by LtWorf » Sun, Nov 30, 2025, 7:29 PM UTC

simonw wrote: post #83

LtWorf wrote: post #78

Earlier quoted context omitted.

Who has ever used github on mobile? I'd like to see their logs about this.

Me, every day.

And what do you achieve by doing that?

Seems a small audience to optimise for.

Re: Migrating Dillo from GitHub

#119

Post by president_zippy » Sun, Nov 30, 2025, 7:34 PM UTC

I freely admit I am out of my depth and have nothing educational to add on the subject. I have but four things to add on this subject:

1. Oh! It's "d.i.l.l.o."! I misread that as something else.

2. After reading many comments in this thread, I must admit I am stupefied at the sheer amount of stuff that can go into merely setting up and maintaining a version control system for a project.

3. I have cited every one of the same problems OP enumerates as my argument for switching new projects over to self-hosted fossil. It also helps a good bit with #2 above when you're a small organization and you're the sole software engineer, sysadmin, and tier >1 support. It's a much simpler VCS that's closer to using perforce in my experience. YMMV, but it's the kind of VCS that doesn't qualify as a skill on a resume.

4. I also find GH deploy keys frustrating because I can't use the same key for multiple repositories. I have 3 separate applications that each run on 4 machines in my cluster, and I have to configure 12 separate deploy keys on GitHub and in my ~/.ssh/config file.

Re: Migrating Dillo from GitHub

#120

Post by llbbdd » Sun, Nov 30, 2025, 7:39 PM UTC

marginalia_nu wrote: post #37

baiwl wrote: post #5

Earlier quoted context omitted.

Having to enable javascript to see a website is not an accessibility problem according to WCAG.

It is a very real accessibility problem if you're using Dillo, which does not support javascript.

it's also a real accessibility problem if you're trying to use sticks and rocks to access the internet