I had to take down the Matrix server lurking
on my Synology NAS because it just didn't have the muscle for it.
So I got a Raspberry Pi 5, configured it to run the raspberry pi OS did
the basic setup from the pi itself and then SSHed my ass in and stuffed
docker and portainer in.
I went with this guide to install Docker. I like it because it tells me what all those various command like parameters are doing and why certain actions might not be a good idea depending on the situation. I love it in fact.
I then went to this guide on the same page to install Portainer. I needed portainer because I was going to kitbash a conduit solution for my pi.
You see, originally I tried to install synapse on my pi and turns out that doesn't support ARM architecture anymore. I tried conduit with a direct install and it didn't write anything to /usr/local/bin/ despite the fact that it should have. So I decided to stuff it in a container.
I knew about this guide for when I was installing it on my NAS. Portainer is doing the heavy lifting. I had to create a different folder to hold the actual conduit stuff instead of what the tutorial uses. I then edited the line "- /volume1/docker/matrix-conduit:/var/lib/matrix-conduit/" to read "- /[newdirectory for conduit shit]:/var/lib/matrix-conduit". On my NAS I edited the reverse proxy to point to my pi's IP on the LAN instead of localhost. And let the whole thing rip. Oh yeah, I have on my setup two extra settings: "- CONDUIT_TLS_CERT=[path-to-my-cert.pem]" and "-CONDUIT_TLS_KEY=[path-to-my-key.pem]" so I got proper encryption going and stuff.
After all that i let it rip.
It's working a lot better so far. I need to juggle plugs so the Pi has some space on an uninterruptable power supply