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

Migrating Dillo from GitHub

dillo-browser.org

Post reply on HN
Print view View original

141–150 of 219 posts

Re: Migrating Dillo from GitHub

#141

Post by nofunsir »

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.…

I used, administered, setup, and customized many on prem gitlab instances for years. I gitlab doesn't memory leak, you're making that up. It's exactly as resource intensive as the number of resources you setup. Can't say the same for JIRA et al.

This comment makes me suspect this entire thread as some astroturfing for that other product.

Re: Migrating Dillo from GitHub

#142

Post by LtWorf »

simonw wrote: post #140
LtWorf wrote: post #118

Earlier quoted context omitted.

And what do you achieve by doing that? Seems a small audience to optimise for.

I file issues, comment on issues, review PRs and increasingly ship code entirely from my phone (thanks to LLM assistance). All of six of these commits today were created and shipped from my phone while I was out and about on a nice dog walk: https://github.com/simonw/tools/commits/47b07010e3459adb23e1... - now deployed to https://tools.simonwillison.net

[flagged]

Re: Migrating Dillo from GitHub

#143

Post by ocdtrekkie »

Kwpolska wrote: post #101

> GitHub has been useful to store all repositories of the Dillo project, as well as to run the CI workflows for platforms in which I don't have a machine available (like Windows, Mac OS or some BSDs). The post does not mention CI anywhere else, are they doing anything with it, keeping it on GitHub, or getting rid of it? > Furthermore, the web frontend doesn't require JS, so I can use it from Dillo (I modified cgit CS…

This was the part that mystified me. Love it or hate it, GitHub Actions is free. Alternative providers like Codeberg have much tighter limits on it, and it sounds unlikely the author's solution includes CI at all.

Re: Migrating Dillo from GitHub

#144

Post by ocdtrekkie »

throwfaraway135 wrote: post #113

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.

One of the things Forgejo has been working on is federation, such that hopefully someday we can replicate the discoverability of GitHub without a central provider.

Re: Migrating Dillo from GitHub

#145

Post by rs186 »

WD-42 wrote: post #30

> 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. The hacker spirit alive and well.

That is an approach very few people would take. I would never do it, as I am sure it would cause me trouble than any potential benefit.

Re: Migrating Dillo from GitHub

#146

Post by flaburgan »

dvdkon wrote: post #107
c-hendricks wrote: post #29

Earlier quoted context omitted.

When I self hosted gitlab I never found the maintenance to be that bad, just change a version in a compose.yml, sometimes having to jump between blessed versions if I've missed a few back to back. Like others, I've switch to Gitea, but whenever I do visit gitlab I can't help but think the design / UX is so much nicer.

My usual impression of GitLab is that it has too many functions I don't ever use, so the things I actually do want (code, issues, PRs, user permissions) are needlessly hidden. What's your workflow that you find GitLab's UX to be nicer than Gitea's?

You can pin those you want in the left menu

Re: Migrating Dillo from GitHub

#147

Post by SoftTalker »

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.

I’d argue they if you can’t prepare a patch diff then your abilities as a contributing developer should be thoroughly questioned.

Re: Migrating Dillo from GitHub

#148

Post by c-hendricks »

dvdkon wrote: post #107
c-hendricks wrote: post #29

Earlier quoted context omitted.

When I self hosted gitlab I never found the maintenance to be that bad, just change a version in a compose.yml, sometimes having to jump between blessed versions if I've missed a few back to back. Like others, I've switch to Gitea, but whenever I do visit gitlab I can't help but think the design / UX is so much nicer.

My usual impression of GitLab is that it has too many functions I don't ever use, so the things I actually do want (code, issues, PRs, user permissions) are needlessly hidden. What's your workflow that you find GitLab's UX to be nicer than Gitea's?

For instance I just got tripped trying to sign out of my gitea instance since the mobile design has two identical looking avatar + username blocks on top of each other, one being the org switcher the other being a menu (with no indicator) with the sign out button.

I went to a project page, and it auto focused the search input (???), causing a zoom in on mobile.

I just prefer the design / look + feel of gitlab more than gitea/forejo. It's not really a hot take, gitlab has been around a lot longer and has much more support.

Re: Migrating Dillo from GitHub

#149

Post by rodarima »

Kwpolska wrote: post #101

> GitHub has been useful to store all repositories of the Dillo project, as well as to run the CI workflows for platforms in which I don't have a machine available (like Windows, Mac OS or some BSDs). The post does not mention CI anywhere else, are they doing anything with it, keeping it on GitHub, or getting rid of it? > Furthermore, the web frontend doesn't require JS, so I can use it from Dillo (I modified cgit CS…

> The post does not mention CI anywhere else, are they doing anything with it, keeping it on GitHub, or getting rid of it?

Yes, we have our own CI service. It is not public for now.

Re: Migrating Dillo from GitHub

#150

Post by simonw »

avhon1 wrote: post #138
simonw wrote: post #85

Earlier quoted context omitted.

A neat thing about GitHub is that every file on it can be accessed from URLs like https://raw.githubusercontent.com/simonw/llm-prices/refs/hea... which are served through a CDN with open CORS headers - which means any JavaScript application running anywhere can access them. Demo: https://tools.simonwillison.net/cors-fetch?url=https%3A%2F%2...

That feature seems common to other git hosts / forges. For example, here's one of Dillo's files, from a few commits ago, from their cgit-based host https://git.dillo-browser.org/dillo/plain/src/ui.cc?id=29a46...

That doesn't have open CORS headers: https://tools.simonwillison.net/cors-fetch?url=https%3A%2F%2...

It's also not being served via a caching CDN, which means I don't feel comfortable running anything automated against it as that might add load to the server that they aren't ready for.

Post reply on HN