so i could stop doing unset($Thing) after my foreach loop.
sometimes i will add overhead with a callable that is immediately called just to keep the scopes clean. its an obsession i have. but that doesn't really work well in templates that are more html than anything.
@bobmagicii@preinheimer But, even without references, once you exit the foreach loop, the variables created as part of the loop syntax (i.e., $k => $v) are still around and hold the values of the last iteration through the loop. So, if you continue to use those variable names, it can result in hard-to-debug issues.
It’s so difficult (and expensive) to run a #Matrix#Synapse server for my own domain. Is it worth it?
I started out wanting to support Matrix, and I've set up a number of channels for my community on Matrix, but everything happens on Discord and IRC right now, and we have a bridge between Discord and IRC, but we can't bridge to Matrix at the moment, so is it even worth it to keep maintaining a separate Matrix presence?
If not, I’m just gonna shut it down. I don’t want to spend the money.
@josh@austin Unfortunately, this isn’t my first hiccup with Matrix, and I’ve tried setting up the other projects mentioned, as well, over the years, each with varying degrees of frustration. I think I just have to face the fact that I’m just not able to get these things working properly, and that’s on me.
I spent about 5 hours tonight getting Conduit set up. The biggest issue is that the download links in their docs all 404’d, so I ended up having to compile it on my own. But then I had to start up a new VM for building it, since the one I was running (1 vCPU with 512 MB of RAM) crashed while attempting to build. (1/5)
After that, I copied the binary to the VM where I wanted to run it, and set up systemd and Caddy. I ran into some issues with the service failing to start, due to some permission errors related to my attempt to use the Debian service file in the repo: https://gitlab.com/famedly/conduit/-/blob/next/debian/matrix-conduit.service
Eventually, I got it running, but it took a lot of persistence and know-how (like knowing how to compile Rust programs and debug things when compilation goes wrong). (3/5)
I will say this: the docs for Conduit are much, much, much more straight-forward and easy to follow than the Synapse docs. I felt confident after looking at them, which is why I decided to go forward with this, even though I ran into a bunch of issues along the way—they were mostly issues I could work around, rather than brick walls. (4/5)
Now, I’ve got it running. There are still a few weird issues I’m noticing, but it’s on a tiny 1 vCPU instance with 512 MB of RAM, and the CPU hasn’t gone above 3% yet, while the memory usage is staying below 40%. That’s amazing! (5/5)
@josh@austin I bumped the RAM up to 1 GB, and that seems to be working well, for me. I’d like to run it on the smallest instance I can, but 1 vCPU and 1 GB RAM isn’t bad.
(It appears @MonaApp removed reply mentions when it auto-threaded my long post, but maybe that’s a feature and not a bug.)
@josh@austin But the best and most important thing about this: the Conduit devs are super-receptive, extremely helpful, and they’ve already acted on some of my feedback. I’m impressed and happy to give that community my support and attention.