[Shameless plug] I've written about migrating my Hugo to Sourcehut and Bunny, leaving GitHub. If you're thinking of switching, you can check it out here:
https://burgeonlab.com/blog/hosting-static-sites-with-github-pages-or-bunny-net/

And if you're interested in trying out Bunny as your static hosting provider or Cloudflare alternative, you can show your support by using this referral code (I get a commission if you become a paying member):

https://bunny.net/?ref=k4vc3x5108

Thank you!

#GiveUpGitHub #github_pages #bunnynet #Cloudflare #Sourcehut #hugossg

Made my first little contribution to @gohugoio documentation yesterday! It's about installing #dartsass in the CI workflow on #Sourcehut Builds, which I'm using to deploy my Hugo site to my static host of choice: Bunny.net.

(libsass is deprecated in Hugo)

I learnt a bit more Git during the pull request too—about rebasing, but I'm still not very good at it (merging the changes is a bit confusing to me).

The actual docs page: https://gohugo.io/host-and-deploy/host-on-sourcehut-pages/

#gohugoio #gohugo #Hugo #CICD #srht

I'm exploring what #GitHub alternatives exist. I have something neat to share.

See the little checkmark on this repo?

https://codeberg.org/louwers/duckdb-builds

The #CI of this #Codeberg repository is running on #SourceHut. Bridged with yojo https://yojo.emersion.fr/

I think each platform has its advantages, but definitely CI is a strong aspect of SourceHut and a weak point of Codeberg / #Forgejo. Both projects are based in the #EU and are open source.

What is your experience with #GitHub alternatives?

Estou migrando para o SourceHut!

https://git.sr.ht/~rodmoi/.dotfiles

#git #sourcehut

No clue what happened to one of my blogs. I just visited it and there's this dodgy looking #recaptcha. I meant to move the #Hugo static files from #Hostinger to #Bunnynet but haven't—doing it now!

Update:
Move to Bunny.net + SourceHut successful! I had to use my own guide as I forgot some steps of using #sourcehut builds #cicd

(I'm a big fan of Bunny, if you want to support me: https://bunny.net?ref=k4vc3x5108)

https://burgeonlab.com/blog/migrate-github-pages-to-sourcehut-bunny

I just have my WP left to move from Hostinger!

#webdev #hosting

Migrating #Dillo from GitHub to our self-hosted server. :blobcatcookienom:

I wrote a post about the current situation with #GitHub and how we ended up self-hosting our own infrastructure to be robust against data loss. We now store all important data (including issues) in git repositories which are replicated accross #Codeberg and #Sourcehut.

https://dillo-browser.org/news/migration-from-github/

@stylus

Yes, of course, I am too, but give https://git-send-email.io/ a try, it really works and the feeling of independence is great!!

And BTW, concerning email lists, those on https://lists.sr.ht/ are good ones. Yes, #SourceHut hosting (not participating in emails discussions and sending patches) is not free, but at least I can see some business plan, which is not to sell my data to somebody.

So much for the federated merge requests via #ActivityPub.

https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358

When I called in https://lwn.net/Articles/963427/ @sir position as the pragmatic one, I was called disingenuous.

(And, BTW, https://codeberg.org/forgejo/forgejo/issues/9225 doesn’t seem to be finished either).

#GitLab #ForgeFed #SourceHut #Forgejo #Radicale

@fasterthanlime #sourcehut and #forejo are the most common ones. If you want a PR-like workflow, then the latter is your main choice. Sourcehut has superb CI.

@fasterthanlime #sourcehut is something to check out I guess, but I feel like you're not into sending email patches around are you? 🙂

@koalalorenzo IIRC, #sourcehut relies on #OVH for DDOS protection.

funnily, I don't need to implement a backend for #sourcehut because they have the proper contribution model already

😆

thanks to @sir for that.

now also on #sourcehut #srht https://git.sr.ht/~matthiasbeyer/git-forge-merge

NixOS Search - Options - Sourcehut.minio
#sourcehut is the only forge for which #minio can be enabled in #nixos 25.05
https://search.nixos.org/options?channel=25.05&show=services.sourcehut.minio.enable&query=Sourcehut.minio

New Linux and FLOSS barrel bags! Get 4 or more FLOSS shirts now and your barrel bag is on us.
https://www.hellotux.com/bag #archlinux #arcolinux #asahi #centos #debian #fedora #f-droid #gentoo #gnu #gnome #kde #linux #linux mint #manjaro #nextcloud #nixos #opensuse #openvpn #postgresql #postmarketos #qubesos #rockylinux #slackware #sourcehut #ubuntu #vlc

I wanted to share my current project. It’s a command line interface for running jobs in the cloud (currently #Scaleway and #GCP) and is a simple way to run your MLOps or data pipelines. Any feedback is appreciated:

https://sr.ht/~ootools/oocli/

#MLOps #MachineLearning #DataScience #AI #Cloud #Python #Sourcehut

Finally setup a publishing the code coverage for a #rustlang using #sourcehut build source.

https://puercopop.srht.site/bliki/cov/index.html

> yjftsjthsd-h

One angle that I'm not sure sourcehut even intends to address but am curious how to idiomatically handle: artifacts. Right now I can (and do) host code in (git|hg).sr.ht and make sure that it compiles with builds.sr.ht, but there isn't an artifacts.sr.ht (and I understand not intending there to be, unless you charge by use and maybe not even then), but it would be nice if I could have the full CI/CD pipeline on sourcehut, including building and publishing final packages. So is the right way to do this to post artifacts to a third-party store (ex. S3) and just stick required authentication in using the secrets support in builds.sr.ht?

ddevault on Nov 15, 2019 [–]

This is actually planned to be supported soon. I recently provisioned a 64TB NAS for the purpose of object storage. It'll support things like release binaries, builds.sr.ht artifacts & build caches, a github pages-esque feature, etc. I just need to figure out how the heck Ceph works.
object store on #sourcehut
https://news.ycombinator.com/item?id=21546671

Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo

Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.

Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.

@matthieufaure @forge sans oublier nos potes (oui nos potes pas nos concurrents) @forgejo et #sourcehut et bien plus encore 😍🤩