I’m beautiful and tough like a diamond…or beef jerky in a ball gown.

  • 28 Posts
  • 177 Comments
Joined 4 months ago
cake
Cake day: July 15th, 2025

help-circle




  • The only reason I gave up on Docker Swarm was that it seemed pretty dead-end as far as being useful outside the homelab. At the time, it was still competing with Kubernetes, but Kube seems to have won out. I’m not even sure Docker CE even still has Swarm. It’s been a good while since I messed with it. It might be a “pro” feature nowadays.

    Edit: Docker 28.5.2 still has Swarm.

    Still, it was nice and a lot easier to use than Kubernetes once you wrapped your head around swarm networking.


  • I had 15 of the 2013-era 5010 thin clients. Most of them have had their SSDs and RAM upgraded.

    They’ve worn many hats since I’ve had them, but some of their uses and proposed uses were:

    1. I did a 15 node Docker Swarm setup and used that to both run some of my applications as well as learn how to do horizontal scaling.
    2. After I tore down the Docker Swarm cluster, I set them up as diskless workstations to both learn how to do that and used them at a local event as web kiosks (basically just to have a bunch of stations people could use to fill out web based forms).
    3. One of them was my router for a good while. Only replaced it in that role when I got symmetric gigabit fiber. Before that, I used VLANs to to run LAN and WAN over its single ethernet port since I had asymmetric 500 Mbps and never saturated the port.
    4. Run small/lightweight applications in highly-available pairs/clusters
    5. Use them to practice clustered services (Multi-master Galera/MariaDB, multi-master LDAP, CouchDB, etc)
    6. Use them as Snapcast clients in each room
    7. Add wireless cards, install OpenWRT, and make powerful access points for each room (can combine with the above and also be a Snapcast client)
    8. Set them up as VPN tunnel endpoints, give them out to friends, and have a private network

    Of the 15, I think I’m only actively using 4 nowadays. One is my MPD+Snapcast server, one is running HomeAssistant, ,the third is my backup LDAP server, and one runs my email server (really). The rest I just spin up as needed for various projects; I downsized my homelab and don’t have a lot of spare capacity for dev/test VMs these days, so these work great in place of that.



  • do GSI roms still contain google binaries (play store, play services, etc…) or is it similar to a AOSP rom where its just a bare android image

    Yes. That’s to say they can be either depending on how the ROM was built. All of the GSI ROM builders I’ve worked with usually have multiple releases of the same build with different configurations: root, no root, with Google services (often MicroG), without Google services, combinations of both, etc.

    To my understanding, GSI ROMs are basically just the “userland” portion of a full ROM. Basically they use the stock/existing kernel, drivers, etc but replace the rest of the system that runs on top of it. If memory serves, they’re possible due to Project Treble. Sadly, they still require an unlocked bootloader to install, so they’re not a total fix-all.

    They’re also very generic generic images (hence the “G” in the term). They’re not optimized for any specific device and can be hit-or-miss feature wise depending on the device. If you’re already reading about a specific device on XDA forums, then you’ll probably be able to see what works and what doesn’t.

    TL;DR: Running a GSI ROM is like upgrading to a newer Linux distro but without upgrading the kernel.








  • I’m about that same age but am so glad we’ve largely abandoned the “www” for websites.

    On my personal project website, I have a custom listener setup to redirect people to “aarp.org” if they enter it with “www” instead of just the base domain. 😆

    server {
        listen              443 ssl;
        http2		        on;
        server_name         www.mydomain.xyz;
    
        ssl_certificate     /etc/letsencrypt/live/mydomain.xyz/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/mydomain.xyz/privkey.pem;
        ssl_dhparam         /etc/nginx/conf.d/tls/shared/dhparam.pem;
        ssl_protocols       TLSv1.2 TLSv1.3;
        ssl_session_cache   shared:SSL:10m;
        ssl_session_timeout 15m;
      
        ...
        
        location ~* {
          return 301 https://aarp.org/;
        }
    }
    




  • Yeah, I didn’t watch this video b/c I’m at work, but I have seen his ebike video so I’m assuming the construction is similarly well thought out.

    It’s just that all the fuses and BMSs can’t protect against a dodgy cell that decides to self-immolate. For cheap, disposable devices that are only meant to be charged 5-10 times or less and then thrown away, I’m super wary of the batteries that are chosen for those. Have seen too many things burst into flames and even expensive well cared-for devices turn into spicy pillows.