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.

Cool, that's a good idea! The granular nginx control definitely sounds nice.

Definitely similar. I really love surge, and have too many static sites to pay the per-site costs to get SSL.

Thanks!

That is unfortunate! Looks like the two projects were started around the same time, too. I may add a note to the site/readme pointing people to that repo if they were looking for it.

Static site hosting is cheap, and I'm not super interested in competing with other services with per-site costs. staticland is primarily an open source project that I use for my own purposes, and I'm open to building out static site deployment projects that fit a company's specific use case based on staticland.

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 / tiny sites and it's really cool I just want to make sure I understand the costs associated.

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 :)

ok thanks, so have you gotten any interest from companies? Asking because I need to host my static sites somewhere soon but don't want to go somewhere that won't stick around a long time.

So far not much interest, but this post is also the first time I've done any significant promotion. If you want to go with a really solid static site hosting company netlify.com seems like a great choice. You could also always set up a staticland-api server on your own. Right now I'm using static.land for 12+ of my own sites that I rely on and more on the way, so it's not going anywhere.

It should be simple to move your static sites if this goes away, don't you think? In fact, I can't think of anything simpler.

Yes. I'll add a note to the site about that. Installing the staticland command-line tool is `npm install -g staticland`

You can get at most of the data via Socrata's API, it's just not necessarily clear how. This new documentation from Socrata helps, though: http://dev.socrata.com/

Thanks! That's a good idea. I've been looking at using cocoonjs in particular as a final chapter on getting js/html5 games into stores: https://www.ludei.com/cocoonjs/

It might still take a few minutes for gh-pages to build the site, but here's the example repo: https://github.com/sethvincent/simple-game-example