Live data from Hacker News

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

fillmem.com

91–100 of 201 posts

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

#91

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 "?".

It's an email share link. It's for you to share with whoever. All of those icons are social sharing icons.

? is actually for the query parameters and that's a properly-formed URI.

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

#92
I use Pelican and host on NearlyFreeSpeech.net behind Cloudflare. I really like using Pelican. I'm hardly a front-end dev and I found it easy to create a custom minimalistic theme that I'm quite happy with. No JS required! Fire up your network monitor and head to https://brashear.me/blog/2017/07/30/migration-from-octopress... It's pretty easy to see Octopress was getting to be a pain in my butt due to ruby dependencies being awful to deal with.

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

#93

I use Pelican and host on NearlyFreeSpeech.net behind Cloudflare. I really like using Pelican. I'm hardly a front-end dev and I found it easy to create a custom minimalistic theme that I'm quite happy with. No JS required! Fire up your network monitor and head to https://brashear.me/blog/2017/07/30/migration-from-octopress... It's pretty easy to see Octopress was getting to be a pain in my butt due to ruby dependenci…

"Ruby is annoying"... then suggest Python :)

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

#94
post #59
post #54

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

I made my first website using vi to make an index.html file in the ~/public_html directory in the home directory of my account on a university Solaris server back in 1997. FTP was a luxury. Kids today.

Can we avoid the ageism?

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

#95

I also used Hugo for my site - https://testloop.co.uk It's so simple.. and FAST. It's hosted on AWS S3 with CloudFront & Route53 so it's not free, but at a cost of around $1.20 per month, it's not far off.

$1.20 a month is really expensive. I have a whole virtual server for €5 a month (and there are smaller ones) that hosts 10+ sites/apps. EDIT: I just realized that's a question I should ask: Does your price include the domain?

$1.20 a month may be expensive relative to your costs, but relative to the average programmer income and monthly bills in the United States – it's nothing. You'll spend three times that cost on a local cup of coffee every morning.

S3 static hosting is far easier to manage than a virtual server; it's a trade-off of convenience vs savings.

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

#96
post #74

Earlier quoted context omitted.

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…

I agree. From the outset it is version controlled, CDN'd, available over HTTPS, and would withstand being linked from the front page of HN just fine. It's not just a static site, it's one that is easy to grow and modify, and that can withstand a lot of traffic immediately with no investment in infrastructure for the author. (evidenced by the fact that it is withstanding a HN front page set of traffic)

Yes, comparing this to throwing up a barebones page at www.somewhere.edu/~username/index.html is apples and oranges.

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

#97

I use Pelican and host on NearlyFreeSpeech.net behind Cloudflare. I really like using Pelican. I'm hardly a front-end dev and I found it easy to create a custom minimalistic theme that I'm quite happy with. No JS required! Fire up your network monitor and head to https://brashear.me/blog/2017/07/30/migration-from-octopress... It's pretty easy to see Octopress was getting to be a pain in my butt due to ruby dependenci…

"Ruby is annoying"... then suggest Python :)

pip isn't great but I've had a much better time with it than rubygems.

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

#98
post #59
post #54

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

I made my first website using vi to make an index.html file in the ~/public_html directory in the home directory of my account on a university Solaris server back in 1997. FTP was a luxury. Kids today.

FTP? You kids had it easy.

We routed console direct to disk in PR1MOS, and if you made a mistake, you had to start all over. But you never knew if you made a mistake until it was done because you couldn't see the output as you typed.

Of course, you didn't end up with a web site, but the result was globally networked. As long as you didn't mind that e-mail took several days to get across the country and a week to go from Illinois to Sweden.

/!killer!jolnet... /Bang paths FTW!

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

#100

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?

It honestly doesn't really matter. Both ingest Markdown, apply a theme, and spit out HTML which you then copy to your HTTP server. It's sort of like asking "which version control do you prefer? Mercurial or Git" or "which build tool do you prefer? clang or gcc." Your choice in the matter doesn't really impact the end result, just your own workflow. Jekyll is probably more popular simply because GitHub has it integrated with GitHub Pages.
Post reply on HN