Redis official site not working because it cannot connect to a redis

Hi, sorry for the issue, the instance Redis.io runs on is very small and has only 1GB of memory, so the OOM killer killed the Redis instance. Normally this was not possible, because redis.io itself uses just a few keys, but lately I installed try.redis.io there, and apparently this uses a lot more keys, I'll have to monitor the keys usage and change the code in order to flush the old sessions faster. The current instance is costing 5$/mo at Digital Ocean, maybe I sent too cheap on this :-D But the idea was that I own everything and don't ask for expenses about Redis OSS official stuff, this was the idea back then. Now no longer makes sense in the new setups but still...

EDIT: just to be a bit safer I set a memory limit in the instance as well.

Btw if you see this as being not very professional, well it is :-D The website was setup by a friend of mine in an afternoon once we upgraded the site to use SSL. I have access and do sysadmin tasks without knowing very well how it is configured (it uses systemd for instance, while I setup things differently usually in my machines). The instance was configured without even a proper configuration file, just a few parameters on the command line. The thing is: we handle this as a "community" thing. And after all considering the near zero-efforts, and the 5$ instance for many many years, it kinda works well.

Anyway all the content is public and open source... (see redis-io and redis-doc repositories), and all our releases are tagged on Github. So the site is not vital in case it goes down for some short time.

Since when dumping out stacktrace and surrounding source code and env is OK for the world to see?

Would have been even more embarrassing if the Redis site was down with a MySQL error

Archive for when this is inevitably fixed: http://archive.is/icwry

This is a bit awkward, but a good reminder that actually 'embarrassing' show stopper bugs aren't necessarily as bad as you think.

As a result of this, here we all are, talking about and thinking about redis. I know I wouldn't have otherwise. It's funny, but stuff like this can turn out to be a net positive once you're over that feeling of 'argh, production went down!' :-)

At least we know they eat their own dog food :-) Hopefully there will be a good post mortem.

Sub-pages work, so you can still read the docs at https://redis.io/documentation

EDIT: Seems that page was cached, it's one of the only ones still working.

I hit refresh like for a solid minute continually & it loaded fine now.

It works alright for me, it loads Redis News.

at least they're dog fooding.

Working right now. Guess they fixed it

isn't the guy from italy, is this related to other news ?