Jekyll Static Web Hosting – Deployment Pipeline on AWS

Post by cirowrc » Wed, Nov 22, 2017, 5:10 PM UTC

ianhowson wrote: post #18

tfolbrecht wrote: post #14

Cool! I could see why this would work well for teams and collaboration. Here's my hugo+aws pipeline for my personal blog. Do editing, with hugo in server mode so I can WYSIWYG edit my pages. Then run a bash script: #!/bin/bash # build site from markdown + template hugo ~/sitedir/ # post to S3 bucket which is a file storage service aws s3 sync ~/sitedir/public s3:sitedirbuckket --recursive # invalidate CDN distributio…

This is almost line-for-line my setup. I like the CodeBuild solution for the times when I'm editing on my phone or a shared computer. I push to GitHub, and CodeBuild handles: * build (as above, plus asset processing and minification) * deploy (s3 sync, plus some fiddling to add 301 redirects) * ping search engines I keep a lot of drafts and temporary notes in my local checkouts and doing build/deploy on a fresh check…

Post by tfolbrecht » Wed, Nov 22, 2017, 5:50 PM UTC

thom_nic wrote: post #32

tfolbrecht wrote: post #14

Cool! I could see why this would work well for teams and collaboration. Here's my hugo+aws pipeline for my personal blog. Do editing, with hugo in server mode so I can WYSIWYG edit my pages. Then run a bash script: #!/bin/bash # build site from markdown + template hugo ~/sitedir/ # post to S3 bucket which is a file storage service aws s3 sync ~/sitedir/public s3:sitedirbuckket --recursive # invalidate CDN distributio…

related: I wrote a plugin to do the same for Jekyll, although it does not (yet) do cloudfront invalidation: https://github.com/thom-nic/jekyll-s3_deploy

Post by bauerd » Wed, Nov 22, 2017, 6:11 PM UTC

bad_user wrote: post #22

I deploy my websites on my own VPS at DigitalOcean, but with a simpler setup then the TFA. I simply have a Travis-ci.org setup that does an "rsync" after "jekyll build". And in case I'm not in the mood for waiting on Travis, I simply "rsync" from my localhost after build. Having an automated build system has advantages though - if you get a PR on your website repository with typos and so on, you just have to merge it…

Post by bovermyer » Wed, Nov 22, 2017, 6:38 PM UTC

AndrewStephens wrote: post #29

bad_user wrote: post #22

I deploy my websites on my own VPS at DigitalOcean, but with a simpler setup then the TFA. I simply have a Travis-ci.org setup that does an "rsync" after "jekyll build". And in case I'm not in the mood for waiting on Travis, I simply "rsync" from my localhost after build. Having an automated build system has advantages though - if you get a PR on your website repository with typos and so on, you just have to merge it…

That's pretty much what I ended up doing as well, albeit with my own static site builder scripts. Each time I build my site[1], the deployment script is just a directory rsync. No mess, no fuss. You are also right about not needing a CDN. My site has occasionally become momentarily popular and my $5 hosting VM hasn't even blinked on my completely static site. A database is a fine thing but you don't want to be servin…

Post by StavrosK » Wed, Nov 22, 2017, 7:04 PM UTC

bovermyer wrote: post #46

johnnycarcin wrote: post #27

Earlier quoted context omitted.

Couldn't agree more. I love tinkering around with things and building setups just to learn, but for something like a personal webpage I just want simple. I use hugo and then setup my output folder (where the generated output goes) as a git repo. Generate the site -> git commit/push -> Caddy. Caddy has a feature to pull in content from a git repo so when you couple that with the built-in Let's Encrypt support it makes…

I also use hugo. In my setup, though, I have everything in one git repo - config files, content files, theme, output, etc. Nginx exposes its output directory. I stopped using Caddy when I discovered that it didn't support one of the unusual TLDs I had. Maybe I should give it another go, though. That was over a year ago.