4 ms·
I like your Travis CI setup, I may copy it myself. Here's the workflow I currently use if the OP wants something with less moving parts. I just use s3_website
by positr0n 10y ago
I like your Travis CI setup, I may copy it myself.
Here's the workflow I currently use if the OP wants something with less moving parts. I just use s3_website from the command line. It will even create the s3/cloudfront configuration completely automatically.
gem install s3_website
; set up s3_website.yml and AWS environment variables
s3_website cfg apply ; this creates and configures the S3 bucket and cloudfront configuration
s3_website push ; push to S3, invalidate cloudfront caches
- kzisme 10y agoIf you're just hosting a static blog website/personal site - is it really worth using Travis on it? I've yet to use it on mine and curious if I should start essentially.
- erikbye 10y agoNo. People add so much unnecessary overhead and bullshit these days. All you need for static is a push from local to your host with SCP. A one-line script if you include some markdown to HTML, or just use Jekyll and straight SCP that.
- kzisme 10y agoI figured as such...I just use Github Pages with my own domain, develop on one branch and push changes to gh_pages...and done. Simple and fast.
- K0nserv 10y agoTo each their own. I actually think this setup is much simpler. I just have to push to git which I'd be doing in any case and it automatically deploys everything. If I were to manually sync I'd both have to remember that and I'd have to figure out a secure way to store the credentials.