Hey! Is Perun (or boot?) smart enough to not re-run tasks for posts/statics which arent modified? I want to setup a blog which will function as my audio blog and every audio file will have a waveform generated with it (via a task) and I don't want to go over all past files every time I would deploy. (poke @martinklepsch)

is this about deploying or incremental builds while working on the blog?

both actually 🙂

when you write a task you can make the task use cache dirs which can be used to cache files over multiple boot invocations/compile-cycles

so definitely possible but more play than plug

@martinklepsch do you have an example of a boot task using a similar approach?

https://github.com/boot-clj/boot/blob/2a7d85f73dbf9db5e9c3e01cd0ddced73b2482fe/doc/boot.core.md#cache-dir

essentially you'd put stuff in a cache dir and also track if the input files have changed, if they did or the "target file" is missing you build it, store the input files shasums somewhere and store the target-file

@jellea

Cache-dir is used between Boot processes

Normally tasks just use tmp-dir

yes but he wants caching

Ah yes

hope that helps to some extent, once you have some code/problems I'm happy to take a look, provide help

martinklepsch great! that will start me cracking! 🙂

I love the getting started guide! 😄

do you?

I feel like we could probably simplify it quite a bit

but well 😄