I'll add two more points: - Remove all non-essential scripts: ads, analytics, fonts, social, liveperson, disqus, truste, foresee, cookielaw, etc. - Scale down or omit images
Not to be "that guy", as I mostly like modern Web design, but: - and after the emergency is over, keep it that way
A Starter Kit for Emergency Websites
111–113 of 113 posts
Re: A Starter Kit for Emergency Websites
#112Earlier quoted context omitted.
That sounds like a really nice approach. Out of interest what does that sort of traffic end up costing on the Cloudflare side - presumably that's where the cost ends up here?
It's a free account on Cloudflare. Cloudflare do not charge for bandwidth... and so it's free. This whole setup is $5 per month for the hosting, though we do use Github personal and that is $7.00 per month.
Re: A Starter Kit for Emergency Websites
#113Or just create a static HTML file and put the damn thing in a S3 bucket behind a cloudfront proxy. That site is virtually guaranteed to never go down even with insane amoumts of traffic (plus it's edge optimized so a user in new delhi won't be sending requests to your server in los angeles) edit: The whole setup takes like less than 2 minutes and can be even automated it with 2 aws cli commands.
care to write a little howto? Thanks!
https://ethanaa.com/blog/conversion-to-static-site-with-vuep...
There are follow up posts on CI / CD and search.