Time to discuss self-hosted alternatives to GitHub!

First, has anyone simply put a bare git repo on a server somewhere, pushed via SSH, and called it a day?

https://idiomdrottning.org/hosting-git-repos

Do you really need more than a remote to push to and pull from, for your personal projects? If you've tried this, what obstacles did you encounter and what features did you miss?

#GiveUpGitHub #SelfHosting #git #SSH #BareRepos

So many ways to host a website.

"These oddball machines are rare on the public internet. But I occasionally bump into them. Like the little servers below that convert sunshine to HTML or squeeze a website from a conference badge."

https://caolan.uk/links/servers/

See also: https://far.computer

Found via @shellsharks excellent newsletter!

https://shellsharks.social/@shellsharks/116499792626342587

#selfhosting #websites

shellsharks » 🔓 2026-05-01
@shellsharks@shellsharks.social

📜 Scrolls issue 39 is out! Getcha some good scrollin’…

https://shellsharks.com/scrolls/scroll/2026-05-01

Thanks to everyone mentioned below. Their work is featured in this week's edition!

@matthiasott @coywolf @jtr @stefan @kaimac @chriskirknielsen @Kaiern @caolan @brennan @JauntyArt @merlin @khleedril @structural_integrity @gelbphoenix @turboblack @anomalocaris @michael @tg @abnv @cwebber @daj @mikepop @csilverman @peritia

#indieweb #fediverse #infosec #cybersecurity

Have a great weekend!

👩‍💻​ My So Called Sudo Life - day 500: still a newbie edition 🆕​

Dear Fedi friends,

Today marks the 500th day of my self-hosting adventures and I'm celebrating it with... a slice of humble pie:

🔗​: https://blog.elenarossini.com/my-so-called-sudo-life/my-so-called-sudo-life-day-500-still-a-newbie-edition/

Also: please remember to update your Linux system to patch the critical vulnerability that has been found.

#Linux #CopyPaste #security #MySoCalledSudoLife #SelfHosting #YunoHost

Hi folks! I would love to hear about the non-standard physical #homelab #selfhosting security measures you've taken. From alarms to boobytraps, from customized IKEA boxes to reinforced closets. The crazier the better!

One requirement: you need to have it implemented (at some point in the past or currently). No concepts that never left the design table please.

Started migrating stuff to the new home hypervisor. gemini://rosarium.vigilia.cc/ is now served from my first OpenBSD VM :) #openbsd #proxmox #geminiprotocol #selfhosting

• users: 1 (just myself)
• following: 254
• timeline_purge_days: 30
• disk: 298m (/var/snac/data)
• ram: 184m (including relayd, httpd, logger, snac itself)

New #blogpost

I have come to share what I've done, some more confessions from a FOSS enthusiast...

https://joelchrono.xyz/blog/more-confessions-from-a-foss-enthusiast/

This is day 53 of #100DaysToOffload

#blogging #selfhosting #degoogle #foss

What bring you to the path of self-hosting?

I guess for me is that because in the mid 2000's the free hosting services were quite terrible and I get my hands on the old family computer and some documentation about Debian.

#selfhosting

Looks like not only backups but also my obsession^Wpassion to write detailed entries to my "selfhosting journal" pays back. Any change, I made in my main home server, has a date and a detailed description of changes made. Also, the process of #NetBSD installation and service installation is documented too, alongside with documented list of running services, opened ports, cronjobs, etc.

At one bad day, my main server started to hangup at near 18:00 and at nea 08:00. There weren't any cron (or any another) jobs at this time. In the logs and monitoring the problems with mosquitto (MQTT server) were visible — somehow it eats at near 100% of CPU, then monit restart it, then things become working, then (after some time) the server hangs completely. Stopped it to see if the problem disappear. But the same problem happens with Prosody. At the end, the root cause of processes slowdown was my PostgreSQL. Investigation showed that write to my second ZFS disk (where the PostgreSQL DB lives) were extremely slowed, so ZFS panicked, crashed and crashes the kernel

[ 204836.661198] wd0d: device timeout writing fsbn 123148477 of 123148477-123148478 (wd0 bn 123148477; cn 122171 tn 1 sn 46), xfer 38, retry 1
[ 204863.837664] wd0: soft error (corrected) xfer 38
[ 206810.672323] wd0: autoconfiguration error: wd_flushcache: status=0x5128<TIMEOU>
[ 212327.420695] SLOW IO: zio timestamp 211326864412007ns, delta 1000556283358ns, last io 211280726737075ns
[ 212327.420695] panic: I/O to pool 'zfs' appears to be hung on vdev guid 1299234741086050345 at '/dev/wd0'.
[ 212327.420695] cpu0: Begin traceback...
[ 212327.420695] vpanic() at netbsd:vpanic+0x183
[ 212327.420695] panic() at netbsd:panic+0x3c
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x15e
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x31
[ 212327.420695] spa_deadman_wq() at zfs:spa_deadman_wq+0xe0
[ 212327.430704] workqueue_worker() at netbsd:workqueue_worker+0xef
[ 212327.430704] cpu0: End traceback...

At the same time, I hear a strange metal noises from server at near 08:00 too, so the destiny of second drive was specified.

The server restoration will take some time, but since anything were written in the log file, I'm able just to replay some actions and get all systems up as soon as possible

#selfhosting #HomeServer

Alt...

Emacs buffer with journal entries (in OrgMode) related to the administrative actions in the server.

Alt...

Emacs buffer with description of NetBSD installation process on the main server and with lists of TODO items, services, opened ports, etc.

Alt...

EGA colored photo of a 2.5 inches HDD

I’ve been playing around with a Rock Pi 4 Plus. Went with the default minimal Debian image, since fighting with U-boot wasn’t something I wanted to tackle yet 😛

Running Caddy on it and hosting https://caddy.ninja for testing purposes.

#sbc #caddy #selfHosting