61–67 of 67 posts
After I discovered Netlify, I'm kind of thinking "why bother". It's free, I just push to my repo and they take care of all the building/publishing/hosting/CDNs, and they're very responsive for support and have high availability. I'm a very happy customer (or rather leech, as I don't pay anything).
I had some static sites on Firebase and moved them to Netlify because the build tools were excellent, not to mention built in form handling.
Earlier quoted context omitted.
I had some static sites on Firebase and moved them to Netlify because the build tools were excellent, not to mention built in form handling.
I use Firebase with Cloud Functions for form handling and other data related tasks (like caching API calls). I'm loving the integration between the two.
I have a preloaded domain that would no longer be eligible (Chrome would keep it around for now, Firefox and their list consumers would prune my entry) for the HSTS Preload list if I were to use Firebase due to lack of ability to include the includesubdomains and preload tokens. :/
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.
New thing for me was using Gitlab CI/CD. I taught the 'customer' how to edit on gitlab website and do merges. Now changes are deployed automagically without needing me to get involved.
Best part, no wordpress databases I need to worry!
Earlier quoted context omitted.
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
Looks good. gzip is implemented on cloudfront instances via a flag, so you can kill two todos by implementing it! I wonder how much cool stuff you could add to this build gem. Minification, staging, SCSS, etc.