Live data from Hacker News

Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

static.land

31–40 of 40 posts

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#31

Earlier quoted context omitted.

So while it may be cheap it's still a cost. Is there a file size limit? What if I statically host CoolLinuxISOs.com? Surely that could end up costly or is it limited in some not identified way? What about handling major traffic from, say, if my website went to the front page of Reddit.com or any other popular website? Can it scale out and handle traffic spikes or even constant traffic? I get this is more for small /…

Thanks, this is an important point. static.land itself may be best considered a demonstration of the open source software. If someone has significantly large files they're looking to host, they would want to host the staticland-api server themselves or consider other options. I'll add some text to the site about this.

Gotcha. So curious, is there anything stopping someone from using up too much of your bandwidth? It's a cool thing but I'd hate to see some spammer get ahold of it and end up using thousands of dollars worth of bandwidth. I mean I'm sure you're monitoring it but you're not always next to a computer to put a stop to it.

Just food for though :)

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#32
post #7

This looks like a nice idea but it's a bit unfortunate about the name clash with https://github.com/rpominov/static-land Edit: Dear downvoters, normally it'd be unlikely for the name clash to matter, but because these are both JS libraries, both available on npm, it's the difference between `npm install static-land` and `npm install staticland` which would be an easy mistake for anyone to make.

From rpominov/static-land’s README:

  Pros  
  
  - No name clashes.

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#33
post #29

Looks just like Surge.sh with free SSL.

I wouldn't recommend Surge.sh. We've experienced a lot of downtime in production and we switched off of it.

I'm sorry you had a poor experience. Our downtime was very unfortunate. FWIW - It was quite some time ago and we have not had downtime since. Of the three occasions we had downtime two were due to our infrastructure provider taking our network down in error over invalid takedown requests and we had to fend of a DDoS the other time. I hope we can earn your trust again and you give surge a shot again in the future.

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#34
post #24

Is this primarily for static sites like Jekyll and Hugo? If so, could you add some kind of tutorial on how to get my Jekyll blog hosted on static.land? I'm not familiar with node, and your docs don't mention how to do a `git push`, only `staticland deploy`. What is the technology behind `staticland deploy`, git, ftp, https?

The deploy command is https. staticland doesn't use git at all, just deals with the built site produced by whatever static site generator you use. I'll add some examples to the docs! Thanks for pointing that out. For jekyll, the short version is you can do something like this: > jekyll build > staticland _site/ yourdomain.tld

+1

Author of surge.sh here. Just want to add my support for the compile locally paradigm over sending to a service to be built. Far less complexity. Far more predictable.

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#35
post #16

Another alternative is to deploy to S3/Cloudfront using Stout ( http://stout.is ).

That looks nice. I use middleman with s3_sync(https://github.com/fredjean/middleman-s3_sync) but I'd have used Stout if I had known about it.

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#36
post #24

Is this primarily for static sites like Jekyll and Hugo? If so, could you add some kind of tutorial on how to get my Jekyll blog hosted on static.land? I'm not familiar with node, and your docs don't mention how to do a `git push`, only `staticland deploy`. What is the technology behind `staticland deploy`, git, ftp, https?

The deploy command is https. staticland doesn't use git at all, just deals with the built site produced by whatever static site generator you use. I'll add some examples to the docs! Thanks for pointing that out. For jekyll, the short version is you can do something like this: > jekyll build > staticland _site/ yourdomain.tld

[deleted]

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#38
post #16

Another alternative is to deploy to S3/Cloudfront using Stout ( http://stout.is ).

Amazing. I've been using s3_website (1.4k stars) and it works great w/ Jekyll and CloudFront as well: https://github.com/laurilehmijoki/s3_website

Re: Show HN: Staticland – Open source static site hosting with SSL via Let's Encrypt

#40
post #27

Earlier quoted context omitted.

Mainly this: * the login to aws. * Then creating S3 keys with the right security settings. * Then tweaking the settings to serve pages * Then setting up SSL with letsencrypt (I have not looked it up, but I'm pretty sure it is possible) * Then configuring CORS if you need it (again, possible with S3) In the end it just came down to workflow. I never really enjoyed working with AWS on command-line or automation. I much…

Just a note on your point about S3 and Letsencrypt: AWS has their own tool for free provisioning of TLS certificates, which is all integrated in a very nice way if you put your S3 bucket behind Cloudfront (which is a good idea). Search the console for the AWS Certificate Manager.

Right this is what I was planning on using. I may still give it a shot, not entirely sure. For static sites I just want something quick and cheap.
Post reply on HN