I really loves Caddy, it has replaced nginx in my go-to HTTP server. It's really simple and powerfull, one nice example is how simple you can deploy applications with zero downtine [1].
On testing HTTP requests, I'd suggest Hurl [2], (I'm one of the maintainer). You will trade Ruby unit tests for a tailored HTTP text file format but I think it can shine for this kind of migration. Tests will be run in parallel, really fast.
For instance, test_site_is_up.rb will be replaced by a simple text file:
GET https://alexwlchan.net
HTTP 200
[Asserts]
body contains "This website is a place to share stuff I find interesting or fun."
GET https://alexwlchan.net/articles/
HTTP 200
[Asserts]
body contains "Articles"
# etc...
Testing alternate domains (test_alternate_domains.rb) could be:
GET http://alexwlchan.net
HTTP 308
Location: https://alexwlchan.net/
GET http://alexwlchan.net/contact/
HTTP 301
Location https://alexwlchan.net/
# etc...
I just installed caddy on my local linux archlinux system , I love golang but I had never bothered installing caddy locally , well it seems really cool , I have currently installed marmite as well locally .
My problem though to moving to caddy is why even pay 5$ when you can get it for free. I have installed it on my pc just for learning experiences :)
I don't get why anyone would use Netlify for a personal website or any website nowadays.
Unless I am missing something, there are places where you can host a website for as close to $0, even if you start to get over 100GB of traffic, wouldn't get a huge uncontrolled bill.
Inertia? I have a small project with basically zero visitors, doing basically zero traffic, being filled with a git commit via cron job every day, happily chugging along for a couple years. Why would I switch as long as it works?
Caddy is great. But why didn't they just put any cdn in front of netlify (or caddy as well)? Not only would it reduce the traffic to the static site to essentially 0, it would serve requests nearly instantaneously from the edge.
Caddy and self-hosting's cool and all, but I think I'd miss push to git to deploy and just not having to manage 'stuff'. Although, I did move a site from netlify to cloudflare (free) and still have this facility.
You could setup a github action(if your repo is hosted on Github) or use something like gitea in your local environment to manage your repo and then you push changes to that gitea repo, it has an action runner like github's which does all the automating stuff for you.
It is only one time setup pain point, after that you are all set.
Netlify's pricing is pretty insane for bandwidth, yeah. They also are quite brutal when it comes to your site getting DOSed or some other form of traffic flood.
On testing HTTP requests, I'd suggest Hurl [2], (I'm one of the maintainer). You will trade Ruby unit tests for a tailored HTTP text file format but I think it can shine for this kind of migration. Tests will be run in parallel, really fast.
For instance, test_site_is_up.rb will be replaced by a simple text file:
Testing alternate domains (test_alternate_domains.rb) could be: Give it a try![1]: https://www.lambrospetrou.com/articles/server-deploy-scripts...
[2]: https://hurl.dev