view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Myself i'm running a instance for two people in a pretty small lxc container on my home server- 1vCore, 512MB of ram and 8GB storage. Currently it utilize around 5% of CPU, ~250MB of ram (+260MB of swap), and ~2GB of storage (nearly 50/50 picts/postgres), in terms of network traffic i see average of 20kb/s, depends how many communities are you subscribed for.
My homeserver is running on i3-4150, 16GB ram and a couple of ssds, using Proxmox VE as hypervisor
edit: typo
Huh, proxmox on a i3-4130? That doesn’t choke on cpu? TBF, I’m assuming you’re running several other VMs. Also, why not docker?
Proxmox itself is pretty lightweight, and yes, i'm also running other VMs and LXC containers (not much, about 9 containers with some lite services like teamspeak server, couple of bots, deluge and hestiacp, prometheus, k3s for testing and "vdi" in vm). Actually - i'm running docker - inside LXC containers. Not the prettiest way to do it, but it works fine
Fair enough. There are no rules for homelab; do what you want!
Out of curiosity, are you running a repurposed 1L OEM box? I’ve picked up a handful of those for dirt cheap, and they’re kinda fun to play around with!
not the one you were replying to, but I'm 2/3 thru switching my servers over to the 1L form factor and am liking it. it's amazing how much compute can be crammed into a tiny space these days.
Close enough! I'm using a HP z230 SFF, not as small as those 1L USFF, but pretty practical for a small homeserver, have a couple of PCI-E slots to expand, can hold 2x HDD (if you count replacing 5,25 optical drive with a tray) or multiple SSD wherever they fit. Pretty happy with this build, day-to-day it draws about ~18-50W from the wall, depends on load.
How are you routing it to the internet?
I use nginx proxy manager to route all my services. Just forward 80 and 443 from my router to that.
I'm using hestiacp to host some websites anyway, so i just added a new nginx template to create reverse proxy to lemmy+lemmy_ui containers
I really want to figure out if it's possible to stick it behind cloudflare or something. I would rather not expose any IP address directly to the internet. I'm leaning on just setting up a reverse proxy on a cheap cloud instance back to my home.
My instance is actually behind cloudflare and it works fine, but remember that it would be possible to "expose" ip of your server due to federation, as your server will talk to other server (directly, that traffic won't go over cloudflare), so if you are paranoid about that, i would recommend setting up a wireguard tunnel to cloud instance, and forwarding the traffic that way, or just setup the lemmy on that instance
Thanks that's kind of what I was thinking. Have you used cloudflared before?
No, i didn't, but i think it should also work over cloudflared