SysOp, Gamer, Nerd. In no particular order.

  • 4 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle







  • Anarch157a@lemmy.worldOPtoSelfhosted@lemmy.worldRevamped install for Piped
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    You can run with your own reverse proxy Nginx if:

    • You expose the port used by the backend/API with a “ports:” setting on the compose file
    • Expose the socket used by the ytproxy container using a volume that points to a directory in the host

    You’ll still need 3 DNS names and a SSL certificate to cover all three.

    TO configure your Nginx, you can use the template I provided on the config/ directory as a base.









  • Join the fight for the right to repair. Manufacturers (I’m looking at you, Apple) have been removing the ability of end users to repair their own stuff and making it more difficult for independent repair shops to do their jobs. Repairing stuff goes a long way in keeping electronics out of land fills.

    But repairing can be understood as “reusing”, but there’s a first step before reusing, it’s reducing. Basically, stop buying shit that you don’t need. If you don’t buy it, it won’t be manufactured, so it won’t end up as e-waste.

    If people minded more the reduce and reuse, recycling wouldn’t be as needed.




  • I already did a few months ago. My setup was a mess, everything tacked on the host OS, some stuff installed directly, others as docker, firewall was just a bunch of hand-written iptables rules…

    I got a newer motherboard and CPU to replace my ageing i5-2500K, so I decided to start from scratch.

    First order of business: Something to manage VMs and containers. Second: a decent firewall. Third: One app, one container.

    I ended up with:

    • Proxmox as VM and container manager
    • OPNSense as firewall. Server has 3 network cards (1 built-in, 2 on PCIe slots), the 2 add-ons are passed through to OPNSense, the built in is for managing Proxmox and for the containers .
    • A whole bunch of LXC containers running all sorts of stuff.

    Things look a lot more professional and clean, and it’s all much easier to manage.



  • Anarch157a@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    1 year ago

    Based on my experience (nearing 30 years of system administration), one thing led to the others. They lost the capacity to handle lots of simultaneous requests when Google cut them off, so they pushed the change to rate limit at API level, but since they don’t seem to have QA or testing anymore, this led to the front-end hitting the limit, but the front-end didn’t have an error handler for this situation, so it just kept trying.

    Tl;Dr, Twitter 2.0 is a shit show.

    It’s actually bellow amateur hour. The best metaphor I can make for how things are working there right now is a bi-polar Chihuahua on crack having an epileptic seizures.