SysOp, Gamer, Nerd. In no particular order.

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

help-circle











  • Go for RAM size. Video editing uses a lot of it.

    Don’t bother with the X3D CPUs, video editors don’t benefit from the extra cache, the problem with the stacked dies is that it makes moving heat out of the CPU harder, so they tend to run at lower clock speeds, so with a normal CPU, you’ll get a little bit more performance on video tasks, while the hit on gaming performance will be minimal, especially if you play at higher resolutions where the GPU will be the limiting factor.

    As for storage, get an NVMe that’s big enough to store the games you’re playing and the video project you’re working at the moment, so access is quicker. for other projects and games you don’t play often, put them on an HDD or NAS with 10Gb Ethernet.

    As for graphics cards, Nvidia has better video encoding than AMD at the moment and great gaming performance, but don’t dismiss Intel Arc, they’re entry-level for gaming, but have a stellar performance in video encoding. Considering the price difference between AMD and Nvidia, you could pretty much buy an RX 7900XTX and an Arc A750 for the same price of an RTX 4080, so you could use one for gaming and the other for encoding. The advantage of this is that you could play games on the AMD card at the same time the encoding is running on the Intel.


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










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