Live data from Hacker News

Building a fast, secured and free static site in less than three hours

fillmem.com

81–90 of 201 posts

Re: Building a fast, secured and free static site in less than three hours

#81
post #35

Earlier quoted context omitted.

Assuming your blog is technical, this would have been a good chance to get some more traffic by at least mentioning the actual domain, linking to the github repo, or having one or both of those in your profile. Edit: Not sure why this has been met with a stream of downvotes. Is there something wrong with saying "I use a different approach to publish this blog: [link]," especially if it's technical and would be of int…

"Edit 2: I don't generally care where a post is but this went from -2 to +6 pretty quickly. Weird?" Probably I can answer that :) I noticed that when one of my posts get down voted even when having a neutral comment, it swings back to positive fast when touching -1 or -2. I guess that the gray comment takes a while for HN'ers to notice as down voted. And when they find that there is nothing wrong with it or they actu…

That is probably it. I sometimes underestimate just how many people are looking at any given thread simultaneously.

Re: Building a fast, secured and free static site in less than three hours

#82

Damn, I must be doing something wrong... It took me three months to rebuild https://www.forthepeople.com as a Jekyll site on a load-balanced cluster from WordPress.

I note that your mailto: links don't include an email address. e.g. at the bottom of the page https://www.forthepeople.com/class-action-lawyers/clergy-sex... the mailto link (black envelope image) has the email address "?".

Re: Building a fast, secured and free static site in less than three hours

#83

I wrote a similar blog post: https://tberra.com/aws/amazon/meta/2016/11/12/the-birth-of-a... The main differences on mine are: - I use Jekyll, which is ranked #1 in the static site generator space. - Hosted on AWS S3. - CloudFront in front of S3. - Routing and aliases handled by Route53. - Deployed using a tool called s3_websites (change detection only uploading generated files AND cloud front cache invalidation for…

I also deploy to S3 largely for operational reasons — it costs nothing unless it's getting pretty significant traffic, and it easily scales up to handle ~infinite volume in case I'm not (unlike say running on Digital Ocean or something).

Another very nice piece of the puzzle is TLS certificate management using Amazon's ACM. It's no cheaper than Let's Encrypt, but it's a lot more convenient. You put it in place once, and you never have to touch it again — Amazon's engineers will deal with hiccups and bugs instead of you. It's no more convenient than CloudFlare, but I like to minimize the number of services my dependency graph.

Re: Building a fast, secured and free static site in less than three hours

#84

After many different iterations, I'm now using netlify (with middleman). Really hard to beat. GitHub pages are amazingly fast and a pretty good default choice. With cloudflare it's a pretty solid combo. But netlify's awareness/integration between the content and the cdn is really compelling. Imagine they'll be able to do a lot more with it down the line too.

Me too. My personal site is in Middleman hosted on a digital ocean instance so I can have more control of that side (also wanted to learn more about nginx and SSL) but lately I've been using Middleman with Netlify - it's unbeatable for getting projects up and running fast.

Built-in continuous integration and automatic SSL, you can even get your domain through them. Their CMS makes creating a fully featured blog ridiculously easy. 10/10 would Netlify again.

Re: Building a fast, secured and free static site in less than three hours

#85
post #79
post #47

Earlier quoted context omitted.

There is a karma threshold before you can see the down vote arrow (underneath the up vote arrow). It was 200 when I got it, it may be up to 500 by now? I don't think they publish the number.

Right, that's why I recently started checking people's profiles before posting a dissenting reply, and not making the reply if they've enough karma to downvote me.

If you care deeply enough about fake internet points to go to that much trouble, IMHO, you're doing it wrong.

Are you feeling picked-on because of what you're saying, or how you're saying it?

Re: Building a fast, secured and free static site in less than three hours

#86
post #79
post #47

Earlier quoted context omitted.

There is a karma threshold before you can see the down vote arrow (underneath the up vote arrow). It was 200 when I got it, it may be up to 500 by now? I don't think they publish the number.

Right, that's why I recently started checking people's profiles before posting a dissenting reply, and not making the reply if they've enough karma to downvote me.

People can't downvote replies to their comments, regardless of their karma count. Also, downvoting doesn't spend karma.

Re: Building a fast, secured and free static site in less than three hours

#87
post #47

Earlier quoted context omitted.

How do you down vote on HN?

There is a karma threshold before you can see the down vote arrow (underneath the up vote arrow). It was 200 when I got it, it may be up to 500 by now? I don't think they publish the number.

I got mine when I surpassed 500 a few months ago.

Re: Building a fast, secured and free static site in less than three hours

#88

I wrote a similar blog post: https://tberra.com/aws/amazon/meta/2016/11/12/the-birth-of-a... The main differences on mine are: - I use Jekyll, which is ranked #1 in the static site generator space. - Hosted on AWS S3. - CloudFront in front of S3. - Routing and aliases handled by Route53. - Deployed using a tool called s3_websites (change detection only uploading generated files AND cloud front cache invalidation for…

I see both Jekyll and Hugo mentioned frequently in the "Using GitHub and X to host your website" space. Do you have any practical our technical reasons for preferring one over the other?

Re: Building a fast, secured and free static site in less than three hours

#90
post #54

Holy cow. Is this an improvement? Remember in 1999 when you could get a static website up in 3 minutes using ftp?

It's actually a good* guide, but the wording of the title seems to me to imply that this is a simple process. It's dizzying complex. * by "good", I mean the following: - prose is engaging - very comprehensive, no hidden steps missed - covers a lot of things that while not strictly necessary, will make an experienced git user's website updating workflow much easier in the long run - covers some small details that are…

Hmm, I found lots of proofreading material.
Post reply on HN