Maintenance and ops doc

[behaviary]

We should create a maintenance and ops protocol/doc for when weird stuff happens like:

[vgrichina]

@potatodepaulo what would be helpful for this specific issue (receiving 502) besides "look into server logs"?

[behaviary]

Hey following up on this: It looks like the server doesn't actually write logs. It's just STDOUT on that console on render. I wasn't ever able to figure out what actually caused this. It was down, then it wasn't. The server restarted at some point, but I wasn't sure why.

@potatodepaulo what would be helpful for this specific issue (receiving 502) besides "look into server logs"?

I'm not sure! I'm thinking I want to write down who has access to what, and how to get it if they don't have it.

[vgrichina]

@potatodepaulo

The server restarted at some point, but I wasn't sure why.

that can be auto deploy on push

we don't have health check setup yet so it's not zero downtime yet

[vgrichina]

or on any env var changes we also get auto deploy