Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
81–90 of 171 posts
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#82For anyone looking for a hosted solution, https://surge.sh/ is super nice and simple without any of the complexity of managing the stack yourself. Deploying uses one simple command, and you get hosting and custom domains for free, though I believe SSL is paid for custom domains. (I'm not affiliated with Surge at all, just a happy user.)
I was mostly going for a DIY solution since I wanted to "own" the bits being deployed while remaining as close to the infrastructure as possible. Providing a hosted service somewhat moves away from the DIY spirit; I suppose additional tools/UIs could be offered to simplify setup and deployment and still run everything directly on AWS, but at that point one might be inclined to just move to one of the other hosted solutions for the simplicity.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#83Earlier quoted context omitted.
There are plenty of reasons even beyond privacy and MITM content changes. Supposedly HTTPS is better for SEO and also there are browser APIs[1] that only work in HTTPS context [1]: https://developer.mozilla.org/en-US/docs/Web/Security/Secure...
If you're building an application that requires the uses of these APIs, I'd hardly call that a static site, but maybe that's just me.
I have several simple games hosted on Github Pages using the storage API which is on that list.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#84Bundling service config and launch makes the whole process easier, for sure. There's also more than one way to configure this depending on what your needs are, so it'd be cool to have a few different versions of SCAR. I started with a setup similar to your diagram and tweaked it when I realized S3 didn't serve index.html when the URL was just the parent "directory", i.e. example.com/foo/ doesn't resolve to s3://examp…
I think that behaviour should be handled with index documents in S3, without the need for lambda: https://docs.aws.amazon.com/AmazonS3/latest/dev/IndexDocumen...
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#85Earlier 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.
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.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#86We use a combination of Netlify + Webflow + Hugo for our website (www.facetdev.com). With that we get a global CDN and our website will never go down. Netlify has been awesome and it made it stupid easy to combine our www site on Webflow with a hugo static blog in a subfolder (/blog). This might be my favorite web publishing workflow ever. If you haven't tried Netlify yet, definitely give it a look.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#87What benefit does this have over Netlify?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#88We use a combination of Netlify + Webflow + Hugo for our website (www.facetdev.com). With that we get a global CDN and our website will never go down. Netlify has been awesome and it made it stupid easy to combine our www site on Webflow with a hugo static blog in a subfolder (/blog). This might be my favorite web publishing workflow ever. If you haven't tried Netlify yet, definitely give it a look.
Does the webflow save to a git repo?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#89Nice project. As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays. I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet. Edit: Thanks for these replies.
What I like about static sites is that you can serve the site in its entirety from a CDN. So you can literally just CNAME www.yoursite.com to yoursite.gitlab.io (or w/e static site host you use). This dramatically cuts down on latency worldwide. It also removes your web server as a single point of failure for short-term outages.
The first hit is brutal. I won't say the CDN since I'm not an expert, but it doesn't take long to go cold (minutes) and once it's cold even the cached hits are 400ms.
Is 400ms really a dramatic reduction in latency?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#90Sorry to nitpick, but "Copyright © 2019" isn't a "license". It's not even a full copyright declaration without listing an owner.
A what? In the majority of the World copyright has been automatic for about 140 years.
How you get copyright is you make a work. No need to put anything else on it. IIRC there are about 3 countries that aren't signatories to the Paris Convention.
In USA you can file a notice in order to get better treatment in court, but it's not been required for 40 years or so, is that what you're referring to?
FWIW the license is very clearly MIT, https://github.com/cloudkj/scar/blob/master/LICENSE.