But I find this “nginx.http.sock” created on “shared/standalone” in the host file system, too. Initially pink, as a socket, but after a while, maybe a stop, it becomes blue, as a directory, and container refuses to start stuck on trying deleting a socket… become a directory.
So, what can we do in order to fix it? Until now, I’m just experimenting, but should I go online with some hundred people connected and hundred thousands post, will I risk to loose everything just because Postgres doesn’t manage abruptly interruption? It will be something to do in order to fix a damaged database. Can Discourse run on external Postgres, something that we can manage if Discourse container doesn’t start? In short, in case of “PANIC” or “FATAL”, there should be some fix…