News for hackers. Stuff that matters.
Re:Static Sites on Heroku by jenius on Sunday June 03, 2012 @10:49AM (#4060844)
There's an even easier way to do static sites on heroku and have them compiled for you - use stasis (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.

Re:Static Sites on Heroku by g3orge on Sunday June 03, 2012 @11:14AM (#4060906)
What's the difference in using nanoc to do that?
Re:Static Sites on Heroku by winton on Sunday June 03, 2012 @08:37PM (#4062186)
I am the creator of Stasis. Compare the sheer length of docs for nanoc (http://nanoc.stoneship.org/docs) to those of Stasis (http://stasis.me), and keep in mind that Stasis can do anything that Nanoc does.
Re:Static Sites on Heroku by jaspervdj on Monday June 04, 2012 @04:41AM (#4063157)
This 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).