Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

github.com

Post reply on HN
Print view View original

141–150 of 171 posts

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#141

Post by clintonb »

jasonlingx wrote: post #133
clintonb wrote: post #75

Earlier quoted context omitted.

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?

I did not. I've used Forestry for over a year. I was not aware of Netlify CMS until shortly after writing my post.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#142

Post by tty2300 »

MarvelousWololo wrote: post #136
Symbiote wrote: post #132

Earlier quoted context omitted.

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?

The usual roadblock in this process is getting ports exposed to the internet. In the best case this can just be done on your router configuration. In the unfortunately common case the ISP blocks you from doing this and the only solution is to change ISP.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#143

Post by tty2300 »

danpalmer wrote: post #55
shshhdhs wrote: post #50

Earlier 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…

When I tested my $5 nginx vps could handle 16,000 requests per second over local host. Maybe at worst 10,000 per second over the network

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#145

Post by sharcerer »

xondono wrote: post #68
nkellenicki wrote: post #63

Earlier 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.

Also, github pages require a public repository (or a pro account), Netlify + github doesn’t

that's a bummer. I thought now that we have private free repos, websites could be hosted there. Still nice feature. I guess, the public nature definitely generates some trust and also is a good way of showing your work as Github works like a project showcase platform too.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#146

Post by jasonlingx »

clintonb wrote: post #141
jasonlingx wrote: post #133

Earlier quoted context omitted.

Did you consider Netlify CMS vs Forestry?

I did not. I've used Forestry for over a year. I was not aware of Netlify CMS until shortly after writing my post.

Ah. I was not aware of Forestry until I came across your post as well. Now I’m not sure which one I should go with.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#147

Post by KingFelix »

mises wrote: post #123
ehonda wrote: post #105

Earlier quoted context omitted.

apt-get install nginx goaccess cd website cp * /var/www/html Yearly maintenance required: apt-get update, apt-get upgrade View traffic stats: goaccess -f /var/log/nginx/access.log I'd say its just as easy and seamless to do it yourself on a cheap VPS for a static website. HTTPS isn't that much extra work either.

Maybe I'm just a security nut, but I would probably also relegate ssh to a non-default port, allow key-only authentication, narrow ciphers, close all other ports (except 80, 443, and 53). Also fail2ban, sysctl tweaks (networking, disable coredumps), and a whole bunch of other things I have in a script. I've seen way too many people get their boxes trashed to leave an internet-accessible one exposed and unsecured.

What are your thoughts on sharing your script? I have a few VPS and would love some new tools / proper setup. I have been learning as I go, learned a few day 1 things not to do, but would like to learn more about networking/coredumps. Cheers!

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#148

Post by vidyesh »

gtirloni wrote: post #38
jaden wrote: post #6

GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify. [0] https://pages.github.com/

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.

Was about to say the same. Netlify is far less complicated and free to run a bunch of static sites with low to medium traffic.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#149

Post by vidyesh »

jasonlingx wrote: post #146
clintonb wrote: post #141

Earlier quoted context omitted.

I did not. I've used Forestry for over a year. I was not aware of Netlify CMS until shortly after writing my post.

Ah. I was not aware of Forestry until I came across your post as well. Now I’m not sure which one I should go with.

I use Netlify and can vouch for its simplicity. I have a few sites on it, some are deployed via bitbucket and some are simply drag-and-drop.

I never used Forestry but by the looks of it, it looks more of an actual CMS and far too sophisticated than Netlify. Being said that it looks over engineered to me for hosting static websites. But if I wanted a CMS to host my client websites whom I have to hand over control, I would definitely give Forestry a try.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#150

Post by viraptor »

ehonda wrote: post #105
clintonb wrote: post #75

Earlier quoted context omitted.

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…

apt-get install nginx goaccess cd website cp * /var/www/html Yearly maintenance required: apt-get update, apt-get upgrade View traffic stats: goaccess -f /var/log/nginx/access.log I'd say its just as easy and seamless to do it yourself on a cheap VPS for a static website. HTTPS isn't that much extra work either.

> Yearly maintenance

I'd say continuous maintenance with response to specific issues. Also debian updates don't restart services which rely on updated shared libraries, which means you need to restart your nginx after openssl updates. Also restarts when kernel is updated. Also...

There's really more to it than just an annual upgrade. You're likely not going to be affected if you ignore this, but why risk it?

Post reply on HN