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.
- No name clashes.
Myelf -- I've migrated almost all personal and small projects over to a self-hosted dokku instance. All of the static sites run this buildpack: https://github.com/dokku/buildpack-nginx
This has been a real timesaver as dealing with S3 static sites was just a pain. Added bonus is I have more granular control of nginx (if I want it)
Excuse my ignorance but what's the issue with S3 static sites? I have a couple I was going to put up shortly and was planning on using S3.
* 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)
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
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.
(not affiliated but I know that the author put lot of thought in it)
>Hire us to set up an internal static site deployment system that fits your use case.
>Use the open source code to host a staticland server yourself. github.com/staticland
I get this is more for small / tiny sites and it's really cool I just want to make sure I understand the costs associated.
Just food for though :)