Ah, I get it. That makes sense. On Wednesday, June 26, 2013 4:32:50 PM UTC-4, Niphlod wrote: > > > > On Wednesday, June 26, 2013 7:07:33 PM UTC+2, Ian W. Scott wrote: >> >> Thanks Niphlod. I'm intrigued by the diffbook project, so I'll take a >> look at your github repo. My main interest is in streamlining my workflow >> (not just webdev, but my academic research and teaching as well) around a >> large folder of flat files that, when changed, will trigger other events >> (like publishing to a blog) automatically. >> >> I think you're right that I've confused this kind of flat-file storage >> with static site generators like Nikola. So I'll have to think more about >> it. >> >> When you suggest auth.wiki() you mean to publish text in blog format, >> right? It doesn't have anything built in to pull in text files--or does it? >> >> Ian >> > > Nope, it doesn't. I was suggesting that in the case you need to have an > actual app running that reads something and outputs the HTML every time it > gets hit by a request. > > That exactly the opposite of the blogging/generator "pattern" of most of > those libraries/projects that you referred to, that needs something > "external" (i.e. a process watching over files, you manually launching it, > etc etc) to trigger a rebuild that outputs the HTML one-time-only (and then > save it to disk and/or ship to a static hosting website) > > diffbook has no source-code on github: as said before it's a "frozen" > version of a "real" app that I freeze with wget and then ship to a static > hosting platform (in this case, github pages). >
-- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
