>png = "./filters/process_png '{{source_file_path}}' 
'{{target_dir}}/{{source_file_name}}'

Yes, the problem is that you know that the output path is 
'{{target_dir}}/{{source_file_name}}' but to soupault that command is 
opaque.
To make automatic caching possible, the output path needs to be made 
explicit.

One compatible syntax I can think of it like this:

[asset_processors]
   png = { target_path_template = 
"{{target_dir}}/{{source_file_name}}.css", command_template = "sass

 >do you have any plans to add caching for asset_processors?

That's complicated. With pages, it's simple since the output path is 
decided by soupault itself.
With asset processors, the user specifies a template for generating a 
complete command.
That is required to accommodate commands with peculiar syntax that makes 
it impossible to just append the output file path,
and to allow original and processed files to have different extensions.
However, it also means that soupault doesn't actually know the output 
path and cannot replicate what  the user-given command would do.

I agree that it would be nice to cache asset processor outputs but it's 
going to require syntax design changes.

Thanks for testing it! I'm planning to make a release early next week then.

On 1/26/23 10:03, nik gaffney wrote:
>
> Thanks! that fixed it.
>
> On 2023-01-26 03:49, Daniil Baturin wrote:
>> Hi Nik,
>>
>> I fixed the problem. It was a funny case of missing parentheses that 
>> made bits of actual logic interpreted
>> as a part of a debug log function body: 
>> https://codeberg.org/PataphysicalSociety/soupault/commit/599f0f921c32b0d5daf41e5ba4fa369f55acb15c
>>

Hi Nik,

I fixed the problem. It was a funny case of missing parentheses that 
made bits of actual logic interpreted
as a part of a debug log function body: 
https://codeberg.org/PataphysicalSociety/soupault/commit/599f0f921c32b0d5daf41e5ba4fa369f55acb15c

Could you try building again and let me know if it works for you without 
debug now?

On 1/25/23 12:49, nik gaffney wrote:
>
> I took a closer look and managed to confuse myself by setting 
> debug=true which appears to avoid the problem.

This is odd. There shouldn't be a need for any other settings, so you 
have likely found a bug.

Is your site source public so that I could test it myself on the same data?

On 1/25/23 10:25, nik.srht@fo.am wrote:
> I've been trying to get the new caching feature to work, but keep 
> getting errors about missing hash files.
>
> [WARNING] Cache directory for page site/crystal/Calibrating Future 
> Experiences.odt does not contain a page source hash file 
> (.page_source_hash),cache will be discarded!
>
> the config includes these settings

Hi Beau,

Sorry for late reply. It looks a bit strange that the main page only has 
a navigation menu,
maybe add some introductory text there or move the content from /about 
to the main page?

I didn't know about caretaker, thanks for the pointer!
I'm going to include it in the tips and tricks section.

In the next soupault release I plan to add caching of asset processor 
outputs
(and other things that call external programs), so pseudo-live rebuilds 
should become even faster.

Oh, indeed! Let me fix it real quick.

On 11/16/22 15:47, toastal wrote:
> There’s a tag up on Codeberg. I tried to build it with Nix.
>
> [source,shell-session]
> ----
> $ result/bin/soupault --version-number
> 4.3.0
> ----
>
> This failed my version test for Nixpkgs so I can’t attempt to bundle
> this package for the ecosystem.
>

Hi Aorthoir,

 >but how do we use a file? is it just lua_source = path.to.file or is 
it file = path.to.file

The "lua_source" is always an inline Lua source, while "file" is always 
a path to a file.
Here is an example of lua_source usage: 
https://codeberg.org/PataphysicalSociety/soupault.app/src/branch/main/soupault.toml#L94-L98

 >site/blog/index.html is the index where #blog-index is located. So all 
files in site/blog will be indexed and added to the div id="blog-index" 
in index.html.

Hi Aoirthoir,


 >Is that 4 options instead of 3?

Indeed! There are only two hard problems in programming: cache 
invalidation, naming things, and off-by-one errors. ;)
I forgot to update the number when I added [file or lua_source], I'll 
fix that.

 >When it comes to index.fields.something, is the something literally 
just any name I want it to be?
 >So that the index.fields.something is just my decision and is not 
related to anything internally in soupault?

Hi Aoirthoir,

I'm tempted to say yes... but in reality, that manual is quite large now,
and it can be difficult to spot missing features.
I'm going to give it a deep look this weekend to verify my claim.

I was also thinking of making a PDF version,
but I'm not sure what's the best approach.
Maybe now that all big things I had in mind are already in place,
it's feasible to make a snapshot "Soupault 4.x Edition" manual.


On 10/11/22 19:44, add1tocobol@add1tocobol.com wrote:
> I am getting ready to dive in hard on Soupault, and want to make sure