5 ms·
There's an even easier way to do static sites on heroku and have them compiled for you - use stasis (http://stasis.me http://stasis.me) - I've built a framework
by jenius 14y ago
There's an even easier way to do static sites on heroku and have them compiled for you - use stasis (http://stasis.me http://stasis.me) - I've built a framework on top of stasis and have been using it for months, as part of very large production sites, and it's been extremely stable and super easy to use.
All you need to do to get them working on heroku is include a super basic config.ru file, and you're all set. The files compile into a public folder which heroku uses to serve them.
- g3orge 14y agoWhat's the difference in using nanoc to do that?
- winton 14y agoI am the creator of Stasis. Compare the sheer length of docs for nanoc (http://nanoc.stoneship.org/docs http://nanoc.stoneship.org/docs) to those of Stasis (http://stasis.me http://stasis.me), and keep in mind that Stasis can do anything that Nanoc does.
- jaspervdj 14y agoThis is not the case, not by far. nanoc is aimed at building complex sites and hence has a lot more features than Stasis. Some examples: - Items can contain arbitrary metadata in nanoc - You can trivially build multiple representations of a single item in nanoc (e.g. a PDF/txt/html representation of a single markdown file) - Dependency tracking in nanoc is fully automatic (no need to specify priorities) - Nanoc is easily extensible using custom filters, custom deployers, custom helpers and more Statis and nanoc have a different audience. To me, Stasis seems to be aimed at simpler, smaller sites, while nanoc is aimed at much more featureful sites. It is a good thing to have a lot of documentation (nanoc is frequently cited as a good example of how documentation should be handled).