Moving to SourceHut

As of now, I switching all my repositories from GitHub into SourceHut. It's an very unpopular 11ty starter, and it's also been running for 2 years (7 stars!). It is always better to prevent than to cure. But why?

1. GitHub is owned by Microslop, which is aggressively anti-consumer, and AI-slopping their products. e.g. Windows, Microsoft Office.
2. Due to 1, you may get AI slop for commit, Copilot, closed-source.
3. Overkill, bloated UI and resources.
4. Networks issues occasionally*, mostly regional issues like in Indonesia.

Otherwise, SourceHut is AI-free, JS-free, and packed with an awesome suites that devs will be use.

1. Tickets/To-do/Tracker/Bug tracking aka Issues or Request to the project which is very straightforward, and easy to use without the terminal advice.
2. Builds, like in GitHub workflows. You need to pay it, and if you looks god, you can get it free.
3. Mailing list
4. Paste, like GitHub gist and Pastebin, also very dead simple.
5. SourceHut pages, an static web hosting that you may use for basic HTML site, Hugo, and 11ty (will try it soon)

A little tutorial

Permanent link

If you think it's too advance for you which is scared to terminal, it's actually very simple.
First, you should create your account before in sr.ht. And then, you can configure your Git credentials and SSH key.

git config --global user.name "Your Name"
git config --global user.email "your_email@example.com"

# and you can check what applied...
git config --list

ssh-keygen -t ed25519 -C "your_email@example.com"
cat ~/.ssh/id_ed25519.pub

and add it to your meta account > keys > SSH keys

In case you have an repo to switch from GitHub to, you can delete the remote first.

git remote -v
git remote remove origin

And then, you can register an repo first with their GUI in git.sr.ht, add the SourceHut remote.

# In case the repo is empty:
git init
git add .
git commit -m "i make blahblahblah..."

git remote add origin git@git.sr.ht:~username/project_name

# View the remotes, you can see something like "origin git@... (fetch/push)
git remote -v

git push -u origin main

FAQ

Permanent link

How do I contribute to the project?

Permanent link

I still can't find an easy and good way to send patches and merge request, for now the most reliable way is git-send-email. You can also submit a ticket, explaining what should I improve and what code I should change.

How do I deploy with SourceHut?

Permanent link

Because it's an SSG, you can simply deploy the _site directory top any static site publishing. The easiest way for me is by using Vercel CLI, Surge.sh, and another.
You can also using their SourceHut pages with hut command, which is used to deploy this website.

tar -C _site -cvz . > site.tar.gz
hut pages publish -d username.srht.site site.tar.gz

Where the Giscus comment features?

Permanent link

It's removed from the code for now until I found an good alternative, as Giscus is using GitHub as the core. Maybe, using Mastodon or Bluesky powered comment section.