interdimensionalmeme@lemmy.ml 1 month ago
I have a G3 and, this might be counter intuitive, but buy an older model that uses DDR3 ram, old ram like that is obsolete and no one wants it, but more ram is more important in self-hosting than fast ram. Of course that limits how much you can do at once, but if you only have 8gb of ram instead of 32 or 64, the lack of ram is going to be very limiting in the sense that you’ll have to run very few things at one time and that becomes cumbersome to manage services “on demand”, starting them and shutting them down to save on ram, instead of letting them all be ready and idle.
Diurnambule@jlai.lu 1 month ago
Ho you should look into setting up services with systemd socket. This solved my on demand issues. I made a script to generate the services and sockets automatically. It became really really fast to add a container which start ondemand
interdimensionalmeme@lemmy.ml 1 month ago
That sounds interesting but my services are mostly in lxc container with dynamically allocated dhcp addresses (I do not wish to maintain a list of static IPs)
And that makes it hard to start them on demand based on incoming connection like you would an httpd process daemon.
My services are only refferred to by hostnames, for instance vaultwarden.lan, but this address does not resolve when the LXC is offline. I guess I could make a static DNS entries in the local dns server and point those to a LXC container orchestrator to stop and start them as they are accessed.
But also, just leaving them all running and ready to answer queries is, so much more convenient if I have the RAM for it.
But I’m sure there are cases where this is the way to go, but I don’t know how to start LXC containers based on sockets without creating static leases and static dns entries, I really like how IP address and DNS names are completely automated on my network !
Diurnambule@jlai.lu 1 month ago
Yeah i didn’t try with dynamic adresses. Most of my services are behind a ngnix so I make most socket point to there. I usually go by IP, that an old work habit. Should try some news things. I played with it with DNS but my DNS name were for a whole “PC” (that was a raspberry pi zero) it work well even when i put a nginx on raspberry zero and services on pi4 I still had to have fixed port and resolvable DNS name. I should try to automate DNS, maintaining an nginx up to date is some time a pain.