Fork me on GitHub
#perun
<
2017-02-07
>
bhagany02:02:52

hmm, I'm second guessing myself...

bhagany02:02:16

while going through the Getting Started tutorial, I ran into a bug with boot-http (details: https://github.com/pandeiro/boot-http/pull/61). Now I just ran into the same thing running http://perun.io locally, but I could swear it worked before. I deleted boot-http from my local maven repo and reinstalled, but same result. If someone has a sec, could you try to run http://perun.io locally, and tell me if it works for you?

bhagany03:02:44

hrm, maybe it has something to do with the boot version...

jjttjj18:02:09

Hi everyone I'm pretty new to perun. I'm trying to display the first few words of each post on an index page (rendered with collection). The :content key that's in the entries passed to the collection rendering function contains the current state of the content in the boot task pipeline, correct? So I'd need to call yaml-metadata to get rid of the metadata, then operate on the resulting string, then render each individual post, in that order? Is there a way with the built in tasks to just access the original content?

jjttjj18:02:14

I ask because the 200ok site seems to use a different order of rendering things, though that's using an older version of perun

bhagany18:02:55

Hi @jjttjj - are you using a recent Perun snapshot?

bhagany18:02:53

okay, then to answer your first question, yes, :content is the current file content at the time collection is called

bhagany18:02:41

I don't quite understand what you're trying to achieve with yaml-metadata though, could you explain that a bit more?

jjttjj18:02:29

ok nevermind

jjttjj18:02:44

I was thinking i'd have to do that to get rid of the yaml content but realized the markdown task does it anyway

jjttjj18:02:50

makes sense now, thanks!

bhagany18:02:09

sure, no problem. feel free to ask if you run into any further problems!

jjttjj18:02:27

great thank you!