Awesome awesome TIL with COLUMNS for some nicer terminal printouts for READMEs and such

A 2-fer... So I want to host atuin and share shell history across my machines on my tailnet I think... it's such a nice interface but I barely use it so I'm sure the features will improve some aspects of my life. And secondly, this section on using systemd is interesting... I hadn't thought to use systemd to schedule container upgrades - sounds incredibly trivial and probably a widely practiced thing now that I say it out loud... Saving here for implementing something... sometime...

Using my server's filesystem + ssh + git-hooks for the simplest self-hosted CI pipelines ever sounds like a pretty cool setup. Probably would lose any cool graphics like GH Actions gives you but for full sovereignty over your code + zero bloat it's an appealing pattern

Dang Waylon! Love these few lines... uv is great, been using it for environment and project requirements management but I didn't realize it was this easy to setup a pep 723 compliant script!

Love this sed -i '1i #!/usr/bin/env -S uv run --script' little gem too - I typically do uv run script.py so I'll see about making this a simple zsh alias for faster iteration on python scripts... I often have AI write quick bash scripts to accomplish things, but it's quite a bit harder for me to read than python, and with the power uv is bringing to the python ecosystem, maybe it's fine to just be a little higher in the programming stack for script-kitty stuff

I have become a huge DHH fan, maybe that means I'm just a basic bish but as I've become aware of who he has I haven't yet disagreed with much that he has to say... And fortunately or unfortuntaely that remanins true with this post about getting involved "at the edge".

I feel like I bounce between "give me bleeding edge" and "give me unshakable stability" on the daily, and there's probably a time and place for both... I think I am prone to take on initial viewpoints and so I don't want to abandon my desire for stability, but man... maybe running Arch wouldn't be that bad, maybe a release-candidate container for an app at home here or there would be an interesting way to give back even a fraction to the FOSS community.

I try to open issues on GH and such when things happen, but I could take a more proactive approach especially with the software that I use more regularly...

Thanks DHH for posting these thoughts, keep em coming!

Apparently docker swarm is still a thing and now I have to try it

Forgejo has a github pages like feature... this might be nice to use sometime as I try to lean into forgejo, but the last thought/bookmark on using traefik + nginx in a compose stack feels simple too. I'll keep it in mind as I explore the forgejo setup at home

After reading it again I missed something. Codeberg pages is not exactly like github pages, seems more like the github readme thing - you have to use a repo called "pages" and then you'll get {username}.codeberg.page... so they own this TLD, and so I'm not sure it's worth exploring this for homelab situations when traefik + nginx or something is pretty simple as well

Looks like a nice way to use git to back static sites, which I already do with my blog but this would be a simple way to centralize some content I like to serve up. Might make it easier to self-host everything as well!

NOTE: this is in karakeep already

As I explore forgjeo this post has a title that sounds very promising! I would like everything to be a docker compose stack for now and I'm struggling a bit with the runner installation - I might be over-complicating it but some parts of the docs aren't as clear as I want them to be - hopefully this post is a good supplement

EDIT:

I've read through this - it's definitely older than forgejo docs on compose, but I like the setup better... It's more of what I would've guessed whereas the official docs have a dind image being used it looks like to proxy the tcp traffic from the runner through to a docker engine running in a containerized environment... now that I say it out loud maybe I do like that better... regardless, looking forward to having some self-hosted actions running before EOD

I'm starting to setup litestream for replicating sqlite dbs of my apps to my self-hosted MinIO instance... only issue is most of my networking assumes client connectivity via tailscale so I whitelist pretty much every accessible domain. This has gotten me in trouble once or twice, and I'm currently in the throws of backing up sqlite from fly.io. The easiest solution for me would be to add egress IP cidr blocks to my traefik whitelisting configuration and wouldn't ya know it - in september 2024 fly.io released the ability to set static egress IPs!