Show HN: Stout – Go-based Static Website Deploy Tool

OT: The use of text-shadow to break the underline on a link where it passes through a descender is pretty darned clever.<p>See the first link to Eager under &quot;Why You Need Stout&quot; to see what I mean, where the underline is hidden where there&#x27;s a descender for &quot;g&quot;.

Are there any cost advantages to hosting a static site on S3+Cloudfront when compared to other services?<p>My first thought when reading this blog was that you can get the same results by placing your static content in an Nginx docker container and pushing it to ECS or Triton.<p>The docker container tagging would also avoid the rollback limitations mentioned in the article.<p>AWS offers so many ways to accomplish the same things, it&#x27;s hard to figure out which solution is the most cost effective.

It seems like this is designed as a s3_website replacement, with file revving? That sounds useful, I use jekyll and have to roll my own revving via weird customized jekyll plugins.

I didn&#x27;t realise I could scroll down at first (13&quot; Macbook Pro)

&quot;The resulting entity body may be short and stout&quot;

Er... pushing a directory to s3 is about 100 lines of python. (if not less) Not sure what else this is?

Nice work!<p>If you&#x27;re interested in an option that guarantees atomic deploys and rollbacks across all files in a deploy (not just individual HTML files), handles instant cache invalidation (no 1 minute wait), and comes with built-in continuous deployment, checkout Netlify:<p><a href="https:&#x2F;&#x2F;www.netlify.com" rel="nofollow">https:&#x2F;&#x2F;www.netlify.com</a>