Put a coffee cup on it, preferably with the moving rainbow gradient for the heat guard. Text should be "Our devs have stepped out for another oat milk lavender latte. The site will be back up shortly."
Still deciding if it's best to do this from the DNS side of things or the netlify side of things. A challenge on the netlify side is that we will currently have two netlify projects until the bingo game and site get merged together.
After chatting with Brian, the optimal way to do this is kill the server. The front end can then just render a splash page upon receiving a 500 error. This would work for the game, but not for the site. The easiest way to kill the site is going to be switching repos on Netlify to a splash page.
Truly, the best way to do this and what we should aim for next year is an EC2 instance that we can (1) set limits on and (2) kill instantly.
Put a coffee cup on it, preferably with the moving rainbow gradient for the heat guard. Text should be "Our devs have stepped out for another oat milk lavender latte. The site will be back up shortly."
Still deciding if it's best to do this from the DNS side of things or the netlify side of things. A challenge on the netlify side is that we will currently have two netlify projects until the bingo game and site get merged together.
After chatting with Brian, the optimal way to do this is kill the server. The front end can then just render a splash page upon receiving a 500 error. This would work for the game, but not for the site. The easiest way to kill the site is going to be switching repos on Netlify to a splash page.
Truly, the best way to do this and what we should aim for next year is an EC2 instance that we can (1) set limits on and (2) kill instantly.