Just use Netlify.
Netlify requires your entire domain moved over for custom hostname/ssl. a deal breaker for most.
mmm, no? You can just CNAME a any subdomain, etc?
Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
131–140 of 171 posts
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#132Am I the only one who still hosts my own static sites on a plain old virtual machine? It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil. Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract. I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many…
I host my site on Apache running on an ARM board in my garage.
I'll consider moving to a VM if/when the ARM board eventually fails, but it's been running for 6 years so far. I have 6TB of storage, which mostly serves as a NAS but includes about 200GB of photos for the website.
There is no deployment process; the web root is mounted by NFS on my desktop. I can share large files with people just with "mv" or "ln -s".
> how many 9s do my personal websites actually need?
My router seems to crash every 3-4 months, and I need to reset it. There's around 15-30 minutes of power failure every year. I don't worry about this.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#133Am I the only one who still hosts my own static sites on a plain old virtual machine? It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil. Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract. I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many…
Maintenance is my primary concern. I deal with software for a living. I want my blog to just work without me having to worry about maintaining the VM. Netlify makes this dead simple. I used to host Wordpress sites for myself and family members. I've now moved nearly all of those sites to Netlify (for hosting) and Forestry (for editing/CMS). I no longer have to worry about malicious hacking attempts, Wordpress updates…
Did you consider Netlify CMS vs Forestry?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#134Earlier quoted context omitted.
I feel like Netlify has set the standard in this area now so I'm curious to learn what's different when I see these projects mentioned here.
Netlify is a great tool, my biggest issue with it (and why I continue to use GitHub Pages) is that the "Global CDN" is a cluster of DigitalOcean nodes, which I don't trust as much as e.g. Fastly in terms of performance and reliability. (Note: that info is from anecdotally looking at Netlify site IPs, I could be wrong)
In terms of reliability I would trust netlify any day instead of github, they're build to serve sites and github is not.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#135Earlier quoted context omitted.
It even gives you a CDN. GitHub Pages is fronted by Fastly.
I tried using github pages with fastly, however it appears when a new site deployment is done, github does not invalidate the fastly cache, in addition to fastly independently caching resources on the site, which can cause broken site deployments for several minutes where it is using mixed cached resources from old and new deployments. I opened a ticket with github support, and they said it was expected behavior. It…
I experienced this as well, wonder if one could mitigate this with some site parameters though?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#136Am I the only one who still hosts my own static sites on a plain old virtual machine? It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil. Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract. I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many…
I host my site on Apache running on an ARM board in my garage. I'll consider moving to a VM if/when the ARM board eventually fails, but it's been running for 6 years so far. I have 6TB of storage, which mostly serves as a NAS but includes about 200GB of photos for the website. There is no deployment process; the web root is mounted by NFS on my desktop. I can share large files with people just with "mv" or "ln -s". >…
Sorry about the ignorance but how do you run it from your garage? What about bandwidth? Could you share the url? Also would you recommend me any guide to get started?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#137Earlier quoted context omitted.
I disagree with encouraging people to do this. You are not accounting for a CDN here, like the post. A website on the HN front page went down yesterday on a $5 VM. And S3 just holds your HTML files, for super cheap. There’s no lock-in concern there. You can easily migrate to nginx in the future if you really want, but start with S3
HN won't take a static website on a $5 VM down if it's set up even remotely correctly. Traffic to a popular link on HN is likely to get on the order of ~100rps max (more likely 1-10rps). Nginx will handle that with no problem. CDNs may make a site a bit faster, but for a static site it's unlikely to make much difference if you're on a good host in US/EU or central Asia. If you're hosting in Australia or Japan, maybe…
Not to mention that most VPS providers to even speak about nowdays use SSDs
For a personal site who the heck even needs a CDN, the only reason I might use that if I put photography website with huge shots or if there's a bunch of videos as well.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#138You've only taken care of the surface-level complexity with AWS. Want to do something more like add a header to the response? Well then, create a lambda, deploy it to the edge, and pay per page view. This is something Firebase is much more elegant at - the initial deploy, and then evolution and addition of features geared to static site deployment.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#139Earlier quoted context omitted.
I had honestly never heard of Netlify. I thought GitHub Pages was the standard, with S3 static hosting a second (more involved) option. EDIT: Googling suggests Netlify offers a build, deploy, hosting pipeline all-in-one box. Which is substantially more than any of the projects mentioned here. These serve a single purpose - simple hosting of static websites.
GitHub will build for you if you use Jekyll.
And gitlab will build for you if you tell it how to.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#140Am I the only one who still hosts my own static sites on a plain old virtual machine? It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil. Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract. I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many…
I switched from S3 to a $5/month VM a while back and it is massively better.