One of the the main reasons why docker and kubernetes take off is they standardized the deployment process. Say, you have 20 services running on your servers. It’s much easier to maintain those 20 services as a set of yaml files that follow certain standard than 20 config files each with different format. If you only have a couple of services, the advantage is probably not apparent. But as you add more and more services, you’ll start to appreciate it.
If you use Tailscale or ZeroTier, you can use the private IP address from those services as node’s internal IP in k3s/k8s configuration, and the nodes will connect to the control plane via Tailscale/ZeroTier network.
I’m actually not sure about that. You might want to test it yourself on your own server before shutting it down for good. See if you can bring up lemmy again after renaming the pictrs directory to simulate deletion.
Just go ahead and close your instance. Your comments are already federated in other instances and will not go away. Example in lemmy.world: https://lemmy.world/u/nix@merv.news
You might want to keep the database and pictrs backup so you can later resurrect the instance again when you found some cheap hosting deals in e.g. lowendtalk.
Yeah, it’s been broken since v27. I’m still on v26 because of this.
How about using code-server and pointing it to your markdown folder? While it’s a code editor, it also has built-in markdown preview. Installation is also easy and doesn’t require docker.
I feel your pain. Just the other day the disk on my home assistant machine died after a power outage and I had to replace it with another disk and restore from backup.
I think on redhat/fedora it uses runc by default and on debian/arch it uses crun by default.
deleted by creator
I believe podman and containerd use runc under the hood so they’re also affected by this container escape vulnerability. You should update it to the latest version.
Might want to check ZeroTier too. They don’t have as much features as Tailscale, but have more relaxed limit. If you can’t decide, you can use both Tailscale and ZeroTier at the same time without issue.
Does the SSL error also occur when you access https://yourlemmyinstance.com from curl without the extra activity+json header?
Another trick is setting up a guest/secondary AP that don’t use pi-hole. When your pihole is down, just switch to the secondary AP. Most routers can setup multiple APs, though not all can setup different dns server for the other APs.
and hosting a VPS with the resources required for this is way too expensive for me.
If you’re ok with using VPS from bottom-tier providers, you can get them for 10x cheaper than the usual cloud providers (or more during holiday sales) on lowendtalk.com.
Try limiting the database connection pool size too in lemmy.hjson. It helped a lot in my instance. I set mine to 30 in a small server with 8gb ram. You can set it to even lower value for lower postgres memory consumption.
database: {
host: dbhost
user: "lemmy"
password: "secret"
database: "lemmy"
pool_size: 30
}
Yeah, this is why I have small swap on my servers. I’d rather the process got killed by the oom killer and got restarted automatically instead of running very slowly and trashing the entire server when it uses too much memory.
Should I setup DKIM, DMARC, SPF and reverse IP lookup?
This is no brainer to setup using mailcow. Just need to copy paste the provided TXT values from mailcow ui into your dns entries.
Mailcow is fantastic and very easy to deploy. I highly recommend it.
Does your server has a big swap space?
HomeAssistant and PiHole are the gateway drugs to selfhosting.