Shadow Unveils Lemmy.ca's OVH Core: Xeon E5-2386G, Cloudflare Shield, and Necessary 3 AM Patches
The Lemmy.ca infrastructure runs on an OVH Advance-1 Gen 2 machine in Beauharnois, Quebec, utilizing a Xeon E5-2386G with 32GB RAM and Object Storage for uploads. The setup shields itself via Cloudflare, which reportedly absorbs 64% of all bandwidth usage.
The community is split on self-hosting strategy. Some users, like standarduser, need concrete specs for a machine with AMD, ECC RAM, and specific I/O ports within a 600€–900€ budget. The main technical fight is between using full VMs for presumed resilience versus using dedicated hardware for better cost efficiency. 'Shadow on [email protected]' noted a required nightly cronjob to restart Lemmy due to alleged memory leaks, while 'just_another_person' cut through the complexity by demanding the build justify its power consumption cost against modern storage.
The technical reality accepts the complexity: the primary poster manages a sprawling setup involving Arr stack, Plex, and Minecraft across multiple older machines. The consensus is not a clean decision; it’s an operational acceptance of the diverse, messy hardware reality required to keep multi-service systems running.
Key Points
The high operational cost of dedicated hardware versus utility.
'just_another_person' questioned if the power consumption of large servers actually justifies the utility compared to modern storage solutions.
The architecture relies on specific third-party services for scaling.
The use of OVH Object Storage and Cloudflare for caching and DDoS protection is presented as standard operational procedure.
Self-hosting requires acknowledging necessary patches.
The site stability depends on a mandatory nightly cronjob restart at 3am PT, admitting to perceived software memory leaks.
Hardware needs for upgrading complex stacks.
Users like standarduser require specific components: AMD CPU, ECC RAM, and multiple SATA ports in the 600€–900€ bracket.
Technical consensus on server setup complexity.
Participants are accepting the functional status quo of the primary poster’s complex, multi-service Docker compose stack.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.