Hi all, new Hugo user here (in the process of migrating from Jekyll on GitHub Pages) and I had a question about using Hugo with S3. I’ve read numerous posts about using aws s3 sync to upload the pages generated by Hugo to S3, but I’m wondering about whether this command always uploads the entire sit…

As far as I know Hugo builds the site completely on generation. Incremental builds have been discussed, but I don’t think that’s on the near-term horizon. However, depending on the complexity of your templates and things like pagination/taxonomies, 1900 posts should build so quickly I doubt it would…

It’s not build times that concern me. My build times are currently running about 10 seconds or so, which is a whirlwind compared to the 5+ minutes I was seeing with Jekyll. My primary reason for asking is around uploads to S3; I don’t want to upload the entire site every time I build if only a subse…

Ah, of course; I see. I use Netlify in part because their deployment is super-fast, but in most instances I’ve found CI solutions at least acceptable, having built many large sites.

The CI solves some of the pain, but when Amazon is charging for bandwidth/requests/uploads etc., re-uploading a massive site every time can also cost money. Netlify is good, but it is also very expensive compared to Amazon if you go beyond the free stuff.

Hey, it’s the Scott Lowe . Welcome to Hugo, Steve. :slight_smile:

I’m not “the” anyone…I’m just another IT guy trying to get ahead. :slight_smile:

Slightly off topic, but I have looked around for a cheap and simple way of adding Let’s Encrypt TLS support and manage my S3 sites without going the Cloudfront path (not that many, and some of them are frankly just domain placeholders for side projects that never took off … yet) … And this project …

I did some experimenting a few months back and found that the s3cmd sync command was the most efficient at syncing changes to S3. Something like this works for me: s3cmd sync --delete-removed --no-mime-magic -M --acl-public --recursive public/ s3://$BUCKET_NAME http://s3tools.org/s3cmd

I have now released v2.0.0 of s3deploy: [image] bep/s3deploy A simple tool to deploy static websites to Amazon S3 and CloudFront with Gzip and custom headers support (e.g. "Cache-Control") - bep/s3deploy Which is effectively a total rewrite.

this is the correct solution s3 sync doesn’t work, but s3cmd is awesome. It can also in one step invalidate cloudfront pages that have changed.

Hugo and syncing to S3

support

Javier_Cabrera May 16, 2018, 4:40am 14

can you explain how to use s3cmd to invalidate cloudfront pages that have changed please?

Topic		Replies	Views
A guide to deploying Hugo behind CloudFront with SSL tips & tricks	1	599	February 12, 2019
Why won't Hugo work with S3? support	11	1528	November 17, 2020
How to deploy a Hugo site to S3 tips & tricks	2	2015	March 15, 2024
Can files and folders in the public folder be uploaded to S3 as is (manually)? support	4	770	August 12, 2022
HowTo: Deploying Hugo on S3 and Cloudfront tips & tricks	29	26693	May 20, 2018

Hugo and syncing to S3

Related topics