ActuallyRuben

I recently had GCC give me the error “returning to the gate for a mechanical issue”, fun stuff as well

Mattermost, it might not be the best feature-wise, but it’s open source, and a university can host it’s own server with SSO

To add on to this, if you’re using some random RAM stick picked out of the gutter, then it might be worth it to run memtest86+. Bad RAM sectors can give some weird unpredictable issues.

At the very least, dollar signs will still matter, due to environment variable interpolation.

First of all, make sure the PostgreSQL username matches as well.

Does your password contain any special characters such as quotes, dollar signs or backslashes? They can have special meanings in yaml, resulting in the password being different from what you’d expect.

There even are still some (shitty) webhosts that require payment for a TLS certificate, because they refuse to support letsencrypt.

I have an ancient Dell desktop (Intel Core 2, 1TB HDD, 2.5GB RAM, one partially corrupted RAM stick) running as server, current uptime is 318 days. I reckon you should be fine, as long as the cooling keeps up.