kylerisse

I was able to confirm that all database controller pods are indeed trying to manage a single database, rather than a single controller pod per database with isolation. Findings below....

This actually exists in the codebase already https://github.com/socallinuxexpo/scale-signs/blob/dbdd1d815394821747e1ac6ca9216722da77b1d7/server/js/clock.js#L4 The reason we disabled it years ago is that the code crashes the clients. That being said, it seems like reasonable feature...

Lets attempt to capture this requirement in #256

hey that's a cool repo for pinning PHP, thanks @nixinator ! it looks like it only goes back to 5.6 thought. That might work. It currently runs on 5.4 in...

Agreed @davidelang but until that happens let’s assume we need to keep running the existing one.

> Another note before I forget: Lets make sure we move the credentials we lay down to somewhere that's persistent instead of `/var` where I currently have them: > >...

Despite my limited involvement with the core team going forward I’ll throw out an opinion. I support the view that artifacts should be distributed. I think s3 is the way...

S3 supports IPv6. I imagine @sarcasticadmin would be willing to setup a AAAA record for his bucket. https://aws.amazon.com/blogs/aws/now-available-ipv6-support-for-amazon-s3/

my suggestion to @davidelang was that our team specifically have a VPS available year round for things like this and storing logs/configs online between shows. Action item for next team...

I don't really want to put my private key on the server, or to maintain a separate one for sudo. Doesn't seem better than `NOPASSWD` in any way, as called...