traches @ traches @sh.itjust.works

Posts

4

Comments

503

Joined

2 yr. ago

You would immediately die in agony. No oxygen and a lot more CO2 in the atmosphere

People like this don’t think it was wrong

jesus christ they’re dumb

Charybdis, hippo, appa, Momo, pabu

If you want to self-host, I recommend a used business thin client, docker + docker-compose, and Tailscale for access away from home if needed. Don’t forget to dump & back up nightly.

Edit: thin client because it beats a pi in every respect and doesn’t run on an SD card. Tailscale because you don’t have to open ports in your firewall and point a public domain at your house.

Or you could use hosted services, neon.tech and turso both offer really generous free tiers for SQL databases.

Or you could use a notebook and pen. Sometimes simplicity is king.

Interesting read, I learned some things that git can do and its’s cool to know it’s possible, but I get the sense that „I’m just used to doing it this way” is the author’s main reason. Making most project communication private is a huge sacrifice, and if all projects did things this way then open source development would be far worse off.

I could imagine an „account-less” git forge that uses email verification to create user sessions that then allow conversation and contribution under that email address and name. You’d have to click a magic link in your email every time you wanted to create a session, but they could be long-lived and you don’t have to manage a password.

Somebody please tell me that sol means titties somehow

They’ve slowed down with those a bit recently, haven’t they?

I’d been considering it for awhile, but thought it wasn’t worth the trouble of switching until I realized just how often I do things the tedious manual way because writing a bash script to do it is so arcane

This is why I finally switched to nushell.

quietly

Dude documentation PRs are legit awesome. Everyone should do them

Edit: no seriously, if you run into trouble with a project and take the time to figure out out, consider adding it to the docs for the next person. It’s not hard and greatly appreciated

The trickier part here his connecting your domain to your raspberry pi and allowing the big internet to access it. You have a few options:

• Set up dynamic DNS to direct your domain name to your (presumably dynamic) home IP address. Assign the rpi a static IP address on your home network. Forward ports 80 and 443 to that address. The world knows your home IP address, and you're dependent on your router for security. No spam or DDOS protection.
• Use a service such as cloudflare tunnel. You're dependent on cloudflare or whoever, but it's an easier config, you don't need to open ports in your firewall, and your home IP address is not public. (I recommend this option.)

Either way, don't forget to set up HTTPS. If you aren't dead-set on using nginx, caddyserver does this entirely automatically.

Bro works in a scif

AMD drivers are baked into the kernel, so you shouldn’t have to install anything specific for your card. Steps I’d take:

• uninstall whatever you didn’t install using your package manager
• check that mesa and rocm are installed through your package manager

With Linux distros, you install almost everything through a package manager. Downloading an installer from some website does happen very occasionally, but 99% of the time it will be provided by your distro.

mechanical advantage

Leave the world better than I found it. Raise happy, fulfilled kids who do the same.

Dude it’s just a phone call to schedule an appointment don’t get dramatic

I’ve been using caddyserver for awhile and love it. Config is nicely readable and the defaults are very good.

If you already have a public facing server for them to connect to then sure.