Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TR
Posts
2
Comments
429
Joined
2 yr. ago

  • 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.

  • 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

  • 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.