Follow

The fire was, in fact, unholy.

But it wasn't adding ElasticSearch for the full-text support that did it. It was Postgres, the main database, being upgraded. It doesn't like that very much, it turns out. I have a workaround process, now, but it's a tad involved. I'll try to streamline it some before the next update.

Sign in to participate in the conversation
AWSWAN Cafe

A place to socialize affiliated with the Without A Name family!