My favourite bit of gamedev lore is the load-bearing jpeg in TF2

@brenns10 ohno now I really want to know what happens if you suspend it

@brenns10 hmm it might be worth adding something about servers being hosted in and administered from the USA, and you will comply with US law enforcement (etc) requests when legally required

tech 

@brenns10
If load ever surpasses 1 server then I’d separate the datastore and application layer, move the datastore to (eg) RDS, and put the app layer in a 1-2 instance ASG

tech 

@brenns10
Honestly under maybe a dozen servers it’s not worth spending a ton of time on automation. I’d be more worried about making sure packages stay up to date and security groups are properly configured.

tech 

@brenns10
An alternative that could be interesting is to just re-deploy everything when you want to make a change, and do a blue/green changeover at the load balancer level

tech 

@brenns10
The questions I’d ask are:
1. What is the impact / effort to fix a server disappearing? Ideally this would be close to zero (eg autoscaling group), or at least not require running any manual commands
2. How much effort is rolling out changes (including updating code and updating/changing OS settings/packages)? The nice thing about ansible, puppet, etc is you define the state you want and it gets you there, whereas scripts might require running things in the right order to work

I changed my name on LinkedIn to “☕️Matthew”, and I finally got an email starting “Hi ☕️,”

Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!