• 0 Posts
  • 14 Comments
Joined 4 months ago
cake
Cake day: January 17th, 2026

help-circle




  • Sure, building your own breadboard computer is much better than playing with some website… However transistors and relays are kind of similar in function, they both gate whether current flows.

    If you are already familiar with transistors, then I agree those are a simpler introduction, however most regular people don’t know anything about a transistor, and they seem a little bit magical.

    A relay however can be grasped by most people just by looking at it in operation. Magnet attracts… Electromagnets only attracts when powered… wire doesn’t conduct when not connected… Wire does conduct when connected… Electromagnet can pull or push wire to either connect or disconnect…

    If you want the solution for the first task (building a nand gate with relays), you can see my solution here:

    spoiler

    Xf2nMW9Tn6nBaAY.png






  • I have my Firefox configured to force HTTPS, so it’s rather inconvenient to work with any non-HTTPS sites.

    Because of that I decided to make my own CA. But since I’m running in Kubernetes and using cert-manager for certs, this was really easy. Add a resource for a self-singed issuer, issue a CA cert, then create an issuer based on that CA cert. 3 Kubernetes resources total: https://cert-manager.io/docs/configuration/ca/ and finally import the CA cert on your various devices.

    However this can also be done using LetsEncrypt, with the DNS01 challenge. That way you don’t need to expose anything to the Internet, and you don’t need to import a CA on all of your devices. Any cert you issue will however appear in certificate transparency logs. So if you don’t want anyone to know that you are running a Sonarr instance, you shouldn’t issue a certificate with that in it’s name. A way around that is a wildcard cert. Which you can then apply to all your subservices without exposing the individual service in logs. The wildcard will still be visible in the logs though…